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
My first VPS was for a Minecraft server so I named it cobblestone. I've kept using Minecraft related names for all my machines since then, and I try to pick ones that are at least vaguely related to the function or appearance of the machine. For example my cluster has brute for the master and piglin01-piglin04 for the workers, but those are the only ones I've numbered.
The exception is my two Klipper RPi's, one is octopi since that's what it originally ran, and the other is named after the model of the printer. For some reason I never named my printers.
I probably wouldn't use a naming scheme like this for production servers though - I'd either go with functional hostnames or something like the periodic table which you can pick from arbitrarily. My home servers and clients aren't cattle though, so I like having a little personality to the names there.