Engineer / Platform / Services
Servers you can rebuild from versioned configuration
The whole setup written down as files, so it can be recreated exactly and never lives only in one person's head.
Wrote 1,000 RBAC rules to secure Linux servers
Enhanced data security by implementing 1,000 RBAC rules for developers, application instances, PostgreSQL, MS SQL, and other Linux servers, preventing unauthorized access; documented with Ansible automation.
Implemented a recorded 1,000 RBAC rules across developer, application, database and Linux access, with documented Ansible configuration.
Provisioned Azure infrastructure as code
Provisioned Azure infrastructure as code with Bicep — Container Apps, PostgreSQL Flexible Server, Front Door/WAF and networking — across the development, staging and production environments.
Provisioned Azure infrastructure as code with Bicep — Container Apps, PostgreSQL, Front Door/WAF — reproducible across dev, staging and prod.
Implemented backups and disaster recovery as code
Configured database backup retention as infrastructure‑as‑code, then audited the recovery position and documented the restore procedure — naming the remaining gaps rather than leaving them to be found during an incident.
Configured database backup retention as infrastructure-as-code, audited the recovery position and documented the restore procedure and remaining gaps.
Infrastructure defined in a repository
Built the company's own infrastructure as 19 Ansible playbooks and 34 roles across 12,065 lines of YAML, converging a live host to a declared state with every play idempotent.
The repository supplies the configuration for rebuilding the declared environment, and the parts of it that were only ever true because somebody remembered…
Public services on a small server
Hosted the company’s public services on a single‑core 512 MB host — a git forge, a web server for seven domains, Tor, two alternative‑protocol servers and intrusion banning — treating 464 MB of usable memory as the design constraint; backup automation is a separate implementation.
The recorded public-service setup ran on a machine that cost less per month than a lunch, and the design is better for the discipline rather than merely…
Hardened SSH to 24 validated directives
Hardened SSH to 24 asserted directives with three‑stage validation — the candidate file, the assembled config, then the daemon's own read‑back — after the read‑back caught the running server silently overriding two of the twenty‑four.
The SSH posture is now the daemon's answer rather than the repository's claim, and the difference is not theoretical — it was already two settings wide when…
Backup automation with an explicit restore method
Implemented restic backup automation with retention, integrity checks and a monthly restore‑test workflow; documented storage activation and live‑restore verification as separate operational steps.
The repository contains the backup and restore-test implementation and documents its activation prerequisites.
Built dead‑ host monitoring
Built dead‑man's‑switch monitoring that pings only while memory and disk are healthy, so a degraded host raises an alert by going silent — and caught six variable names saying "free" where the check correctly measured "available", an order of magnitude apart on a 464 MB box.
The host gained an alarm that fires when the expected signal is absent, and the misleading names were corrected.
Made Ansible check mode tell the truth
Made check mode tell the truth across the whole platform after finding six probes deciding on a value the host never gave, because Ansible's command module reports success under --check while skipping the command entirely.
A dry run now either measures something or says it did not, and neither of those is the third option it used to have.
Added a one‑second preflight for secrets
Added a preflight play that runs the same code as the converge against operator‑local secrets in about a second, after a half‑applied production run died on its ninth task with the swap settings already written to the live host.
A secret that does not resolve now costs a two-second refusal on a laptop instead of a partly-applied change to a live server.
Reconciled a 20‑record DNS zone as code
Reconciled a 20‑record DNS zone declaratively against the Cloudflare API with separate audit and BIND‑export entry points, and turned the CDN proxy back off on privacy grounds after building it.
The zone is versioned, comparable and exportable, and the one decision that went against the obvious default is written down with its reasoning so that nobody…
Cut systemd sandbox exposure on every unit
Cut systemd sandbox exposure across every unit this platform installs — a dead‑man's‑switch service from 9.6 UNSAFE to 1.5, an internet‑facing git forge from 8.3 EXPOSED to 1.5 — and added a converge‑time parser check after finding a misspelled directive silently ignored in three unit templates.
Every unit runs with the privileges it needs and not the ones it does not, the numbers are measured rather than asserted, and the class of defect where a typo…
Your code on your own server
Deployed the company's own git forge on Soft Serve, private by default with no web panel and its SSH port bound to loopback behind a jump host, and made the landing page in front of it a build artefact of the main site rather than a hand‑kept copy.
The company hosts its own code on its own hardware, and the page in front of it inherits every check the main site passes rather than drifting away from it in…
Provisioned a second server from code
Automated the provisioning of a second server on a second cloud provider, creating the firewall before the machine so it is born behind one, with both providers' firewalls written directly against their REST APIs to avoid a third‑party collection.
A second host can be created, or re-adopted, from the repository, behind a firewall that already exists, at a cost the file states.
Split every operational secret per host
Split the four per‑host operational secrets after establishing that two hosts sharing one dead‑man's switch alert less than two switches, not more, and that a shared backup passphrase can expose both hosts' backups, even in separate repositories, if someone obtains it and can read both repositories' encrypted data and key files.
Secrets are per host by construction, and the two failure modes that would have followed from sharing them are written down where the next person edits the…
Rehearsed the forge CI hook, found 2 defects
Rehearsed the forge‑side CI hook and found two defects unreachable by reading the file: a fallback that put an unresolvable argument on the hook's input, and git's own environment variable following the gate into the checkout and turning 19 tests red.
The hook works on both paths and both defects were found before any real push met them. The limit is that a rehearsal is still a simulation: it proves the…
Published a readable Tor onion mirror
Published the site as a Tor onion mirror on a readable address beginning engineer, with the key generated off the host so it never reached this repository or a laptop, and left it the one front door of four that is never counted.
The site has four front doors onto one build, and this is the only one that is never counted. Gemini requests and Gopher connections are tallied per day with…