More Control with a Self-Hosted CI Runner
Set up your own build runner on a VPS to control the environment, cache, and cost of your CI pipeline.
NetBay journal
Practical guides for Linux, containers, CI/CD, self-hosting, and running VPS infrastructure from Netbay Engineering.
599 articles · 24 topics
Set up your own build runner on a VPS to control the environment, cache, and cost of your CI pipeline.
Publish a .NET worker as a Windows service using sc.exe or New-Service, configure recovery, and keep logs on High-Speed SSD disk after reboot.
Take a consistent Redis RDB with BGSAVE, copy dump.rdb off the VPS, and restore it on a fresh instance without mixing live AOF files into the recovery.
Unstick a hung Gunicorn or Uvicorn worker with py-spy, journalctl, and a few process checks so you fix the stall instead of blindly restarting.
Point DNS at your Lucknow DC01 origin, measure real RTT, then put a CDN in front so global GETs cache at the edge while writes still hit Lucknow.
Route requests by URL prefix to separate backends and rewrite paths cleanly with Nginx, without leaking internal URLs or breaking deep links.
Discover how dedicated CPU pinouts and enterprise SSD storage arrays yield 3x IOPS performance compared to traditional cloud VPS providers.
A methodical path for containers that exit immediately: state, logs, inspect, exit codes, and interactive reproduction that finds the real cause fast.
Evaluate the real cost of running Mailcow on a VPS, from the Postfix and Rspamd stack to deliverability, DNS records, and IP reputation challenges.
Decide what belongs in each pipeline stage so mistakes fail early and builds stay fast and predictable.
Control who can do what on your cluster with RBAC roles, role bindings, and service accounts — scoped to small team needs.
Centralize container logs, apply rotation before the disk ever fills, and search your whole self-hosted stack from one place when things break.