machstem

I self host pterodactyl for the kids, and my *rr stack, jellyfin + some funky process of using my kids camera roll cloud backups, and sync the shared album up with an rclone cronjob that keeps all our stuff we do together, from each of our individual cameras, and they're all on jellyfin for anyone to watch, any time.

Keep memories alive with mkdocs and write poetry for others to access over a nicely crafted markdown+css web page

Self hosting has kept me sane from my own suicidal ideation and depression since the mid 90s.

We're with you

1

1 yr. ago

Jump

Why is starting with Self-hosting so daunting?

If you've never gone and built your own system, or started a network from scratch without a container based system, and you've relied on stacking your own environment for a long time, you might necognize it as you would any skill.

I'm sure I could build a shed, for E.g. I know to get the wood, the panels, the cement, and all the things I'll have all documented in front of me.

Then I will start, realize I forgot I also needed a permit, which I then found out I might also need to run power to it, so now shed has become something that doesn't feel impossible, it feels daunting

Why? Well, I don't build sheds, I don't keep building things that would allow me to have all the framework, project of getting my shed built. So, as with a homelab, take it one step at a time, and if rhe shed isn't the house, you're allowed to skip a few things and stick with what works for you.

I use homelab and self hosting as a passion, but I also have 25 years of networking and systems administration experience so docker and containers just made my normal, tedious job of building up complex network infrastructure, feel like a job, and my homelab and self host happens to be a hobby

Treat your homelab as a passion or simple hobby, or use it as a skill building tool for work

Overall it's just time, experience and expectations that either drive you forward or set you back

1