It's interesting to consider this genre, the "community website". The primary functions are chat, forums, maybe a wiki or a blog. So a "community website" is a

It's interesting to consider this genre, the "community website". The primary functions are chat, forums, maybe a wiki or a blog. So a "community website" is a union of all the modes people use to communicate on the web. Therefore the solution is going to be a curated compose.yml that runs best-in-class versions of each thing with baked-in identity configuration and its own strong community around data movement between processes. Imagine a website that helps users build their own compose.yml based on their choice of components, similar to https://start.spring.io/ https://start.spring.io/. However, even if you had this, the "exercise for the reader" will be substantial: get a domain name and a host, learn to admin linux and docker. Finally get the compose file and run it. And learn to troubleshoot each process, with its unique runtime and build, when things go wrong. This is a heavy investment, but probably worth it. Kind of like learning to work on your own car.