Engineer / Platform / Categories
Linux & Servers
Built the company's first observability dashboard
Developed and launched the company's first observability dashboard, providing real‑time system performance insights and data visualization on the large office TV.
Built the company's first observability dashboard for real-time system insight, helping teams detect and resolve incidents 40% faster.
Ran 10 Postgre and MS SQL servers on Ubuntu
Designed, deployed, and maintained 10 PostgreSQL and MS SQL servers on Ubuntu Linux VPS, ensuring optimal server performance and reliability.
Designed and maintained 10 PostgreSQL and MS SQL servers on Ubuntu Linux VPS at 99.9% uptime, with 30% faster queries via tuning.
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.
Managed 30 Ubuntu Linux VPS instances
Managed 30 Ubuntu Linux VPS instances, implementing disaster recovery strategies and ensuring optimal network configurations.
Managed 30 Ubuntu Linux VPS instances with tested disaster-recovery strategies and solid networking — a resilient foundation to grow on.
Managed 8 WireGuard and IPsec VPN connections
Managed and troubleshot 8 WireGuard VPN and IPsec VPN connections, ensuring secure communication across Google Cloud and Linux systems.
Managed and troubleshot 8 WireGuard and IPsec VPN connections across Google Cloud and Linux, ending recurring connectivity outages.
Administered network infrastructure
Administered network infrastructure for over 1,000 servers, ensuring optimal system deployment, security, and troubleshooting.
Administered network infrastructure for 1,000+ servers, ensuring reliable deployment, solid security and prompt troubleshooting.
Automated SSL/TLS certs for 100 Docker apps
Automated SSL/TLS certificate creation for 100 Docker applications, ensuring secure connections across Ubuntu Linux hosts.
Automated SSL/TLS certificates for 100 Docker apps on Ubuntu Linux, ending manual renewals and the outages expired certs cause.
Administered 100 Bare Bone servers
Administered 100 Bare Bone servers, physical networks, and IP telephony systems, ensuring robust infrastructure for company growth.
Administered 100 bare-bone servers, physical networks and IP telephony, providing the robust foundation the company grew on.
Administered 40 websites on Apache and Nginx
Administered 40 websites on Ubuntu Linux hosting servers with Apache and Nginx, ensuring high availability and performance.
Administered 40 websites on Ubuntu Linux with Apache and Nginx at high availability and performance — hosting clients never had to think about.
Ran 24/7 support for ~1,000 IPTV/OTT servers
Provided round‑the‑clock 24/7 infrastructure support for an IPTV/OTT streaming platform, administering ~1,000 servers plus client‑owned systems for global customers in China, the US and Germany.
Provided 24/7 infrastructure support for an IPTV/OTT streaming platform — ~1,000 servers plus client systems across China, the US and Germany.
Kept IPTV streaming signals running non‑stop
Ensured uninterrupted delivery of IPTV streaming signals between suppliers and clients, monitoring and maintaining the streaming network and IP telephony around the clock.
Ensured uninterrupted IPTV streaming between suppliers and clients, monitoring and maintaining the streaming network and IP telephony 24/7.
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…
Three locks on the door, none of them locked
Found and closed three SSH brute‑force protections that had never worked: a ban jail watching port 22 while the daemon listened on 1986, a rate limit shadowed by a broader rule above it, and a ban action whose binary never resolved, so no ban had ever applied.
Three protections that had never once fired now do, and the class of defect they belong to — a control whose failure mode is that it keeps reporting healthy —…
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…
Proved the intrusion ban works every run
Proved the intrusion‑banning path end to end on every hardening run by banning a reserved test address, reading the resulting kernel rule and unbanning in a guaranteed cleanup block, so a jail that stops working fails a run instead of reporting healthy.
A banning path that stops working now fails a converge instead of continuing to report healthy, which is the only property that mattered.
Verified firewall rules by position
Verified firewall rules by position rather than presence, reading the numbered rule list and the live packet‑filter chain, because a rule that exists is not a rule any packet reaches.
The firewall posture is now checked the way a packet experiences it. The most useful outcome was not the check but what it revealed about the reporting that…
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.
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…
Built 7 read‑only host reporting roles
Built seven read‑only reporting roles that render a live host to Markdown — facts, access, git, metrics, traffic, security and provider inventory — under a rule that no number is printed the run did not measure.
The estate can be described from the repository on demand, and the reports have found real things: the two dead security controls, an undeclared listening…
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…
Ran containers on Podman and Quadlet
Deployed a container plane on Podman and Quadlet under systemd rather than Docker, because Docker's default bridge‑port publishing can bypass UFW rules — and gave deploys an unprivileged user with one fixed command instead of root.
Containers run under the supervisor that was already trusted, behind the firewall that was already declared, and a routine release uses one scoped command…
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…