The web server deployment model breaks at hobby scale
1–10 of 74 posts
Re: The web server deployment model breaks at hobby scale
#2I guess that breaks the plug-and-play nature, but you can't expect something internet-facing to be plug-and-play. (Maybe that's the real travesty here.)
Re: The web server deployment model breaks at hobby scale
#3Re: The web server deployment model breaks at hobby scale
#4I can fiddle with the page content in Developer Tools to make it work, but frankly, WTF, especially since Immich expects people to set up a reverse proxy for HTTPS access on their own and does not help them in any way (like providing a pre-configured caddy in their compose.yaml, I don't know)
Re: The web server deployment model breaks at hobby scale
#5Re: The web server deployment model breaks at hobby scale
#6Re: The web server deployment model breaks at hobby scale
#7I'm not sure I understand this post. Is this talking about self hosting Caddy in a home lab setting or just static web hosting on a VPS?
Re: The web server deployment model breaks at hobby scale
#8How many of these problems PHP solves out of the box or makes irrelevant?
Re: The web server deployment model breaks at hobby scale
#9It’s fine to publish recommendations how to tune configurations for specific usages. But I only need the app, not the various things that you may think I need. And I really want the app to only solve its essential problem. It should not take care of the IT part other than providing configuration samples.
Re: The web server deployment model breaks at hobby scale
#10I host a webserver for a living, so I might be too far removed from the problem; I don't see anything that 1 minute of effort as part of a less-than-10-minute session with an agentic AI tool can't solve safely. A decent README and project structure is all Codex/CC/Pi needs. I mean this even for the least-technical person who would be self-hosting something. I guess that breaks the plug-and-play nature, but you can't…