Organizing VPS Providers, Domains and Cloudrons

[LoudLemur]

We are running a website without Cloudron on VPS 1.2, and would like to keep that going whilst using Cloudron to install some additional software on that site. What would be a good way to achieve this?

We already have a couple of other sites with Cloudron. Would we need an additional Cloudron account?

We wouldn't need to go into VPS 1.2 and install Cloudron there, would we? Cloudron is already installed and running on VPS 1.1 and VPS 2.1.

[luckow]

aehm. confused I am.
What is your definition of a Cloudron Account?
Goal is: Migration of the website on VPS 1.2 into a Cloudron instance.
The question/s should be:

• A high traffic website that interferes with other applications/websites on an existing Cloudron instance. -> separate instance
• Customer needs full control of a Cloudron instance -> own instance
• Customer uses other apps on the "shared" Cloudron instance in addition to its website -> separate instance
• A low traffic Website from a friend or a customer without a budget -> shared instance
• Whether you need to go into VPS 1.2 depends on any existing long-term contract. Sometimes it is cheaper to use the remaining term and then switch to another provider or product.

[LoudLemur]

@luckow said in Organizing VPS Providers, Domains and Cloudrons:

aehm. confused I am.
What is your definition of a Cloudron Account?

Hi, @luckow! Thanks for asking. In this case, I mean the sort of account at cloudron.io which allows you to use Cloudron and install applications. We are generously allowed up to two applications on one such account gratis. To install more than two applications, we need a paid Cloudron account. It is this sort of paid Cloudron account which I have in mind.

You mentioned "separate" "own" and "shared" instances. I am not sure about the distinction between separate and own.

One sort of scenario I am investigating is something like this, where the client would be concerned only with the application, and would (hopefully never need to use the cloudron.)

Lets say I have an incredible server with 256GB of RAM, gigantic nvme drives, and processor with 96 cores. Could I setup a Cloudron account on that monster and then start pointing it at VPS around the world, in Europe, Asia and the USA and start running unrelated websites on all these different servers from the monster? For example, a Discourse on a Hetzner in Deutchland, a Grav on a Linode in Greece, an Immich on an SSDnodes in India, and a Wordpress on a Vultr in Wisconscin?

[jdaviescoates]

@LoudLemur said in Organizing VPS Providers, Domains and Cloudrons:

then start pointing it at VPS around the world,

Not until 8.0 with multi-host exists. And even then we don't know what the details of that will be yet.

At present each Cloudron account or licence is per server/ VPS.

[LoudLemur]

@jdaviescoates said in Organizing VPS Providers, Domains and Cloudrons:

@LoudLemur said in Organizing VPS Providers, Domains and Cloudrons:

then start pointing it at VPS around the world,

Not until 8.0 with multi-host exists. And even then we don't know what the details of that will be yet.

At present each Cloudron account or licence is per server/ VPS.

Thanks, that is a very clear and satisfyingly easy to understand, helpful answer!

So, in the Monster VPS scenario, all those different websites would have to be located on the monster, at the moment.

[luckow]

@LoudLemur It all depends on your role between the apps/websites and the Cloudron instance. The moment you are a service provider for your customer and, let's say, you are only responsible for the initial installation and onboarding (the rest is up to your customer), that is my definition of own from the customer's point of view. He is fully responsible for all costs and responsibilities (aka super user).
Separate is a perspective from a service provider's point of view. You are responsible for the infrastructure and because of the "high traffic website" (in my example) you decided that you need a separate / dedicated VPS because of bandwidth, RAM or CPU.
Shared in my definition is a viable decision between cost and app usage. Most VPSs are powerful enough to run a lot of websites with low traffic. And if Cloudron's user/group management is appropriate for your use case, shared infrastructure is good for the cost and the environment.