I've been doing this architecture on single tenant VMs for like 6+ years now and it has so many advantages for deployments, security and scaling.
Pretty much every new tool and agent computer I set up uses this pattern. I've blogged about it and created a template repo.
https://housecat.com/blog/the-hugs-stack-hypermedia-unix-go-... https://github.com/housecat-inc/scratch
There is advantage to keeping to "classic" tooling especially if you are not in an "I" context but in a "team" context. How large is the team that is going to use and maintain this custom tooling?
This is exactly what I say, use "classic" tooling in a team. No need of a panzerfaust to kill a mosquito.
And repo is ai documented. AI is everywhere, there is no reason to put notice on everythings. Move with your time. I don't put notice on everything that I build it on linux.
> there is no reason to put notice on everythings. Move with your time.
That is, in fact, the literal purpose to putting notice on everything. Put a notice so we know to move on with our time! If you can't be bothered to even write why your project is interesting, it's rather absurd to expect other people to spend time reading it.