Selfhosted

60587 readers

1517 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:

Detailed Rules Post

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. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Lessons For Round Two..or three.. or- (piefed.zip)

submitted 1 month ago by other_cat@piefed.zip to c/selfhosted@lemmy.world

13 comments fedilink hide all child comments

Hello everyone!

I did it. I reached a point where I got everything exactly how I wanted and now... Now I am dissatisfied as I look over my home lab's chaotic mess of a setup. This was my first time selfhosting things, and I learned a ton of stuff. I'll probably want to tear it down and start anew in the near future, being much tidier and mindful of what goes where.

Does anyone have any tips they want to impart to someone who's not an entire newbie but still learning stuff? Kind of a "If I could tell myself this before I set everything up, I would say..."

you are viewing a single comment's thread
view the rest of the comments

[–] probable_possum@leminal.space 2 points 1 month ago* (last edited 1 month ago)

Make it maintainable.

Documentation. Or implicit documentation with ansible or the like (opentofu).

Separate things with LXCs or VMs or OSI containers. Maybe firewalls (ufw) and VLANs to separate them. Incus is nice. As someone already said: Leave the host system mostly vanilla. Services go in the virtual boxes and containers.

Btw: Nix looks promising, too. But I have not opened that can of worms, yet.

Backups...

Automation. unattended-upgrades, ~~watchtower~~(unmaintained) or the like. So you don't have to do it yourself and then forget about it. Claude is looming on the horizon. It will bring many bugs to light and code the exploit for it in no time if someone asks for it nicely.