view the rest of the comments
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!
Personally I use corporate-like naming scheme for my devices, the format is:
[AABB-CCCC-DDEE]
AA: Location of the device - HQ (home), CL (cloud).
BB: Role of the device - HV (hypervisor), SV (server), NW (network) and workstation (WS).
CCCC: Device brand (for NW), application running (for SV), and workstation purpose (for WS).
DD: For server and workstation - OS running on the device (WN=Windows, LX=Linux, MA=macOS). For network device - their role on network (RT=router, AP=access point, SW=switch).
EE: # of the device, year of purchase for WS.
For example, here's my router, KASM server and my gaming PC hostnames:
Still trying to optimize this naming scheme, like removing all the dash, but currently too lazy to do it lol.
My kubernetes cluster is k3s1, k3s2, k3w1, k3w2, etc. My load balancer is called... lb.home.lan. I guess that we are not as creative.