You can do that just fine. You can order a minimum of five PCBs and choose to have only two assembled. Then you'll get three unpopulated PCBs and two assembled ones. That's a way to get finished PCBs very cheaply.

Be aware that every component that you use that is not in their basic and preferred extended parts library incurs a one-time three-dollar fee. This hurts disproportionately if your entire design is low count and low cost. So if you always go for the latest and greatest ICs as advertised by TI, instead of the Chinese jellybean clone, you'll add up hidden fees quickly. However, when I choose components, I start out on their basic parts page and only go for a non-basic part if it's not there and I really need it.

Or just order the parts with their sister company LCSC and assemble yourself. It's not that hard especially if you have a hot air gun!

Fair enough, http is enough - I anyways have one caddy to rule them all. However, if your app is picky about reverse proxying, e.g. headers, please add a sample caddy config. It's often the first thing I'm looking for if I'm trying out a tool and want to host it under a subdirectory before configuring a subdomain.

No, HTTP is not enough, I submitted a couple HTTP-only links to HN lately, they got flagged within half an hour, even HN crowd can not open HTTP links anymore ;-)

That's not really HN's fault but all modern browsers will warn the user before accessing an http site with a security warning.

My point was not to use http only as a finished solution, but to let the admin front the http-only service with their TLS termination solution of choice.

We are talking about hobbyists here.

... Of which (TLS terminators) caddy is IMO the easiest for hobbyists, as was the starting point of this subthread

I already commented on this twice here, but here it goes again:

I self-host Immich with Caddy as TLS terminator, and it's far from obvious.

They all run on a small N150 PC in my closet, the same PC serves as my internet router. Both Immich and Caddy run in podman-compose, and there are firewall rules that allow incoming traffic to Caddy and outgoing traffic from Caddy to update certificates. There's also a tricky setup of Systemd dependencies that make sure podman networking and firewall rules play nicely together and with other system config, like the bridge for the 2.4Gz range internal Wi-Fi and for external 5Gz Wi-Fi 6 card.

If not for the LLM help, I would have spent many days figuring out all the rough edges of this setup.

Which is exactly the point OP is making. Hobbying webhosting is hard nowadays.

As a one-person-scale selfhoster that has wrangled Apache and nginx before, I'm also saying go for caddy straight away.