CloudLinux is literal meant to always be connected since it’s designed for a Server Use Case. The entire premise is for Servers to Better Manage Users so it’s def not a Desktop intent.
The idea of CloudLinux is to say, create a user and allot this user a certain amount of CPU, RAM, or even burst-able resource envelope in a shared hosting environment.
Honestly so much of this is a deprecated idea if we all move along and start running small containerized deployments anyway.
As long as I the term "cloudLinux" doesn't imply it has to be connected to the internet constantly, I'm fine with that.
CloudLinux is literal meant to always be connected since it’s designed for a Server Use Case. The entire premise is for Servers to Better Manage Users so it’s def not a Desktop intent.
The idea of CloudLinux is to say, create a user and allot this user a certain amount of CPU, RAM, or even burst-able resource envelope in a shared hosting environment.
Honestly so much of this is a deprecated idea if we all move along and start running small containerized deployments anyway.
oh, okay, so it's designed around an intranet then, using individual computers as terminals...
My internet is flaky af, so an "always connected" OS just wouldn't be an option.
Plus I wouldn't trust something like that as far as i could throw it, honestly... too open to abuse...