· ☕ 4 min read · ✍️ Mark A. McFate
This morning, Tuesday, September 17, 2019, I awoke to find our server, and all of the services on it, unreachable via the web. I managed to open a shell on the host and found that the server was up-and-running as expected, but a quick docker ps command indicated that one of the key services on the server, namely Traefik, had stopped and then failed to restart, repeatedly.

My dockerized-server Config
· ☕ 3 min read · ✍️ Mark A. McFate
This post picks up from where Configuring DGDocker2 left off. In it I will establish a workflow to setup a “Dockerized” server complete with Traefik, Portainer, and Who Am I. It should be relatively easy to add additional non-static services to any server that is initially configured using this package.

Configuring DGDocker2
· ☕ 13 min read · ✍️ Mark A. McFate
My mission today is to successfully migrate the images/containers/services chronicled in post 030, “Dockerized Omeka-S: Starting Over” to Docker-ready node dgdocker2 without compromising any of the services that already run there. Pushing WMI Omeka-S to Production on dgdocker2 Grinnell’s dgdocker2 server, specifically dgdocker2.

Removing Traefik's Weak Cipher Suites
· ☕ 2 min read · ✍️ Mark A. McFate
Most of the servers I deploy to and manage here at Grinnell College are now “Dockerized”, and all of those use Traefik to manage traffic, of course. Before a web app or server can be opened for access to the world here, it has to pass a vulnerability scan, and I’m not privy to the specifics of that scan.