Code added in 2016 and pruned in 2018, as we don't use it anymore. So all is fine.

I wonder if we'll keep rSTAGING.

The correct course of action is to:

We'll revisit this after Kubernetes cluster is ready, as that will drastically change the scope of Dwellers (development and build server for Docker images).

Ysul at 12.1-RELEASE-p2 everywhere.

Tested a build manually successfully with:

Kuma is perhaps a better approach for a service mesh.

Assigning back to @inidal for config change against rSAASMW.

Database created

It's already committed as eec9c1bf.

We're now happy with Cachet, and it's fully configured with T1598, let's keep it.

Done manually for testing on Dwellers, but this creates the question about how to manage the wildcard certificates: should we share account and provision them in the acme config files on each server? does acme would follow several cname with contradictory information?

Requires py37-GitPython (map.jinja offers a packages dictionary to get the py37- prefix)

There are also 2015-09-19 files on Dwellers, for a Docker container:

Tests should be extended to development servers and made optional, as we don't currently have an Apache working.

So, it works for two years. Let's restrict root login.

Proxy is fine for DevCentral and other Phabricator containers, per T915 / D484 / 892cd0a35934.

OpenSSH now mitigates this.

Can't repro with current Etherpad version.

Done everywhere now, I've installed Salt 3000 and Python 3.6 on Dwellers.

We do'nt use sshguard anymore, as login by password is disabled, keys are required.

Now at https://github.com/docker/docker-ce/tree/master/components/cli/contrib/completion