Yes, but that’s why I was saying that over time I can always upgrade to a higher plan with more resources. It was never my plan to stay on that… plan… for a long time. I’m just trying to avoid unnecessary costs when testing the waters, you know?
Can you point out a few reasons why I would want them separated, other than the server resources? Right now, I don’t see a good reason to have them in separate servers, but I’m always willing to learn a few different perspectives on things I don’t know yet.
That’s a very interesting point, that I didn’t know about. So it seems that it is indeed something that has been done and it works. Good to know.
What do you mean by parent site? Wouldn’t each installation be independent? Which one would be considered parent?
I’m a bit confused, because when I look at the app.yaml file, there’s a dedicated part for the brevo email and credentials. You said that I can go the route of having individual app.yaml files per community. So, wouldn’t that mean that each community would have their own Brevo credentials, including the notifications email?
Things that will prevent me from backing up properly, or notification emails not being sent properly, things like that. Again, as a non-expert, and still new to Discourse, there are things that other people might see as an issue, but I don’t see it yet.
Yes, that’s what I was thinking. The only shared thing would be the server itself. Everything else would work as a separate installation, hence the question about the email, above.
I think the most challenging steps for me, were already taken, which was to dive deep into installing Discourse a few months ago. I had zero knowledge about it. I didn’t even know what “docker” meant. At this point, I have a much clearer perspective, while still consider myself a “basic Discourse user” when it comes to self-hosting. And with the help of both this community and ChatGPT/Claude, I’ve been able to learn a bit more and take notes on how things work and are installed. I’m ok with challenges, and let’s be honest: this is really just installing software. It’s not that I’m building a nuclear bomb 
If something goes wrong, delete everything, back to a single installation per server. All good 
As I mentioned, I have my own community installed already, so I believe that the hardest part is already out of the way. I’m good at following instructions and asking questions, so as I try things, I can always pause and do some research, take notes, etc.
My goal now is more about understanding the mechanics of it, the pros and cons, what is possible and what’s not, so I can make some good decisions that I won’t regret later on that will require me to spend too much time fixing things, you know?
So, all this information you guys are sharing today is super valuable, because it’s giving me a good idea of what to think about. Especially when you mentioned that the managed hosting offered by Discourse’s team is a multisite. That really made me see that this is possible. Maybe requires a few more steps, but everything can be done.
Really appreciate your feedback 
