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
I used to invent "funny" names, but at some point it became a chore and I also found I'm forgetting some names or spelling when I need it.
Call me boring, but doing enterprise system admin jobs for years I recently started to adopt functional naming convention.
This is what I have now: [location code][OS code][type vm/ct][environment code][workload][index]
So the first production DB linux VM in my primary Los Angeles location will be named LA1LVMPDB1 And my second test Nextcloud container hosted in the same location will be named LA2LCTTNC2.
I still have to invent short names for workload, which is harder for specialized containers, but overall this makes it all more manageable.