Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
No one should be powering off their servers. Thats really not the way to go about anything. Now there’s nothing stopping you from doing that either if you want to and it makes you happy or your life easier.
But if you want a simple answer to a simple question, no, nobody sane is doing that lol
We power off servers in the enterprise all the time and on schedules 😂. Its called saving money.
Uh, in your “enterprise” maybe lol.
In pretty much any enterprise using the public cloud. Everything is auto scaling, so shutdowns when not needed. Dev environments shutdown over night... If you're not shutting down and scaling in the public cloud, you're doing it wrong.
Ok scaling is not what we’re talking about here lol.
Is it shutting down servers... Yes. it just does it based on parameters and thresholds.
Then you get things like VDI servers and jump boxes that only need to be on between certain hours, so get shutdown outside them hours.
No Donny it’s not. You’re out of your element here.
They're fuckin' nihilists dude, they don't believe in anything
But it is. They're stopped and deallocated. They start up when demanded. And shutdown when below a threshold or a certain schedule.
I’m starting to understand why British admins are paid so much less than their American counterparts.
You do understand, when you have VM's set to auto scale, they shutdown when not in use, if you're using horizontal scaling.
Most of us don't have clusters so shutting down the server means taking the server and all associated services completely offline.
Do you take your product completely offline for 8 hours every single day?
Right you don't shut them down, you scale them down. My server also uses less power off peak demand.
No we shut them down. They get deallocated the same way as shutting down a virtual server does. They're not containers, the scaling part just turns them on and off based on workload or schedule
I see where your head is at here, but it sounds like you're focusing on containerized items. A lot of people are going to look at you real weird if you think of scaling down a container as equivalent to shutting down a server. We can all see where your mind is going and there is logic there, but it's more akin to closing chrome when you're not using it than it is to shutting down the computer running chrome.
Even physical hardware, if your paying power you can have clusters of physical hardware power up and down based on usage. There is no point in having 10 physical hosts running when the workload for n+1 means 3 servers overnight. With bnc, ipmi, ilo, idrac it will power them up as needed.
Finally someone who gets it.
Yup. I run those kind of clusters. But unless your in home datacenter territory, that sort of config isn't likely to happen in self hosted.