Asko Nõmm

Currently each blog gets a {name}.itypd.com domain for their blog, which is fine, but I'd definitely want people to also own their content and brand identity, and so having custom domains coupled with fully exportable data is critical. Fully exportable data is a much easier thing to do, but custom domains, well, not.

ITYPD is hosted on Laravel Cloud right now, and while it's a bit pricey, I've been very happy with the convenience of that product. Namely, I've not needed to edit a config file, not even once. It just works. However, it has strict limits on custom domains, and I also need to add them programmatically, so Laravel Cloud quickly becomes a blocker for that feature.

I figure I need to spin up my server where I can control the cert generation parts myself, and then write a API that lets me do all that magic from the service itself (or a service worker). I wonder how (if at all) can I avoid having to restart the HTTP server in order to create new server configuration reflecting any new domains (perhaps I can make it dynamic?), but I think that's the way.

This does mean a lot more work on my side though - deployment pipelines, database management, worker management, security - things I'm not all that great in, but I think it's worth the effort.