Multi-Tenant Support on Cloudron
-
Lets say you have only one Cloudron instance.
Also, to keep things simple, you only want one application running on it, for example, Grav.Currently, can you run several different Grav websites using just that one instance?
For example, could you do this:
MyGravWebsite.com
and
MyOtherGravWebsite.comrather than this:
grav.example.com
grav2.example.comThe last I heard, this feature was on the Cloudron roadmap. I think we could expect it in 8.0
Are we on track? -
@LoudLemur what’s the reason not to just setup multiple instances of Grav?
-
L LoudLemur marked this topic as a question on
-
L LoudLemur has marked this topic as solved on
-
Hi, and thanks for looking at this thread!
Lets say you wanted to focus on one thing, eg Grav websites. If you wanted to serve different clients, you would need to run Grav on different domains. It would be more convenient to administer everything from one instance of Cloudron.
Girish has the term I needed: multi-tenant setup.
I see this won't be happening. I can mark this as solved.
-
This post is deleted!
-
I was thinking that you could install several e.g. Grav on one Cloudron. Each Grav would be on a different domain, eg
Each of these would be on the same cloudron. Each would have different content, e.g. cats, dogs, mice. Each would be found on a different domain, e.g. grav1.com, grav2.com
The thinking is that by having multiple deployments of Grav on the same cloudron, one could manage many different websites using one cloudron instance. So, your cloudron could be on:
and instead of deploying grav to gravcentral.com sub-domains, you would deploy them to entirely different domains, e.g. grav1.com
-
@LoudLemur said in Multi-Tenant Support on Cloudron:
I was thinking that you could install several e.g. Grav on one Cloudron. Each Grav would be on a different domain, eg
Each of these would be on the same cloudron. Each would have different content, e.g. cats, dogs, mice. Each would be found on a different domain, e.g. grav1.com, grav2.com
The thinking is that by having multiple deployments of Grav on the same cloudron, one could manage many different websites using one cloudron instance. So, your cloudron could be on:
and instead of deploying grav to gravcentral.com sub-domains, you would deploy them to entirely different domains, e.g. grav1.com
This setup currently works in Cloudron. One Cloudron server, multiple Grav apps w/ each app on a different domain or subdomain.
-
@humptydumpty Thanks. Grav requires 256MB of RAM
If we had 3 Grav running on the same instance, would we need 3x256 RAM or just the 256?
-
@LoudLemur I believe it's 3x256, because Cloudron gives you a warning when you're trying to install new apps that would put you over the VPS' total available RAM. IIRC, you could proceed with the installation anyway. What matters is how much each Grav app actually uses. Most of my apps don't use the recommended RAM. For instance, Chatwoot has a recommendation of 3 GB but in actuality, mine idles at 766 MB. I don't use Grav so can't comment on that, but this has been the case for all my other apps. The RAM spikes during certain tasks like importing/exporting, updates, and other heavy tasks, but I think you'd be fine with less than the total recommended RAM.
-
The 256Mb is just the initial upper memoryLimit set for apps. This does not mean that much memory is also allocated. Anyways memory usage heavily depends on the usage of the app as such and how many parallel active users are using an app. Usually all this is very hard to define upfront and needs to be tested in real conditions.
