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
Since messing around with Linux more than 10 years ago, I always had the idea of self hosting something myself on a headless PC.
Until last year, I had the bad habit (for today's standards) to host everything on a single machine. My Linux server was my SMB file server, mail server, torrent daemon, minecraft server, firewall, and so on.
Last year, thanks to what I learnt with vmware at work, I decided to install proxmox at home, bought a couple of old PCs so that I could have a 3-nodes Proxmox cluster, and a separate machine for proxmox backup server.
Everything that was running on a single OS before, now has its own VM (for shit like Windows) or LXC (for most of the stuff).
You can say I'm a bit of an old school user now, so maybe you can understand me if I think that running lemmy, inside a docker compose for lemmy, inside its own container, inside proxmox, sounds like a weird recipe for a lot of overhead.
It seems all the cool stuff on github now always have the instructions that start with "step 1: install docker" which, honestly in a virtualized environment, I'm not sure we still need it.
Anyway, back to your post, I tried to follow both the "docker" and the "from scratch" documentation but they're clearly lacking some steps because I failed miserably every time I tried.