this post was submitted on 03 Apr 2026
99 points (99.0% liked)
Selfhosted
60320 readers
476 users here now
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.
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!
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Sooo, that example wasn't exactly "contrived" - it's based on a standard I see where I work.
This is more what I'm arguing against - embedding meta-data about the thing into its name. Especially when all of that information is available in AWS metadata.
[Site][service][Rack]makes sense for on-premise stuff - no argument there.Agree
Not to butt in into your conversation, just wanted to drop that me and my colleagues use what we call the "clone cars" method to combat our company's naming scheme
So for example we dubbed CAPROD01 "Cappy" NASPROD01 became "Nasir" LTPDEV02 became "Luigi" (because he's always number 2)
Of course in written communication we use the full name (which is much less of an inconvenience) and we always double check in conversation or spell out full names before doing anything critical