Operations: roll out, monitor, restore
Software isn’t finished when it works, it’s finished when it runs on your side and somebody there knows how.
How I work
I have worked with Docker and Jenkins since 2017. What I hand over at the end isn’t only code but a pipeline anyone on the team can trigger and a runbook that is actually correct. The sentence I work hardest to avoid is "works on my machine".
That includes the uncomfortable half. A backup that has never been restored is not a backup. Monitoring nobody reads is a comfort blanket. So every handover includes one real restore and the question of who actually gets called at night.
Typical jobs
-
01
Automating deployment so a release doesn’t need a night shift
-
02
Monitoring and alerts that match the cover you actually have
-
03
Setting up backups and rehearsing a restore for real
-
04
Containerising an application and seeing the server move through
-
05
A test environment close enough to production to be useful
With what
Docker, Jenkins, CI/CD pipelines, nginx and Apache, Plesk, Linux, monitoring and alerting
Where you can check this
This site runs on a basic hosting plan with no Node process, from a reproducible build, with the measured sizes on the site board. The workshop also holds an upload service that moves gigabyte files without a server daemon of its own.
MoreOften goes with this
All servicesWhether it’s a specific project or just a question for now, write it down the way you’d tell a colleague. You’ll get a reply from me, not from a mailbox.