Loading feed…
Lobsters0 Hot0 comments12 min read
the web server deployment model breaks at hobby scale
A developer narrates the compounding frustrations of building a web application intended for self-hosting at hobby scale. Each seemingly reasonable architectural decision — offloading static files to a reverse proxy, adding caching layers, splitting a JavaScript frontend from a non-JS backend, using a PostgreSQL extension for multilingual full-text search — creates new deployment burdens for end users. The post traces how each optimization that works cleanly in a professional environment (where you control the full stack) becomes a support nightmare when you can't assume what infrastructure admins have. The story ends with the developer bundling everything — reverse proxy, cache, Postgres with extensions, frontend, backend, and a process supervisor — into a single Docker container, effectively recreating the professional deployment model inside a container, just to restore the simplicity they originally wanted. The final image of a scraper triggering this entire chain of HTTP parsing for a two-year-old page underscores the absurdity.
Source: https://w.on-t.work/web-deployment-model. 8 Sync News only summarizes and links out; content copyright belongs to the authors and original sources.
