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 know linux isn't for everyone, but self hosting on windows is self-inflicted punishment. It's just not the right platform. Sure it's doable, but it's death by a thousand papercuts.
also Ubuntu will add more complexity to things, Debian will cover most of what you need.
I wish I knew this before I started.
But my headless Ubuntu is working now, so I am not changing it.
Don't rush it. You will have plenty of opportunities to change into Debian when your Ubuntu stops working.
Be me whose server is on Ubuntu 18.04 and needs upgrading to get Bluetooth into home assistant 😭
For what it's worth, I usually install Ubuntu Server instead of Debian because it comes with a few more things out-of-the-box that I would install anyway. I have several installations of 22.04 that have been upgraded since 16.04 and they work no problem. (I also have a few Debian installations working similarly well.)
I made my jump from Ubuntu Server to Debian when I containerized everything onto a single proxmox machine.
How so?
Took maybe 5 minutes total to install paperless-ngx in docker on a Debian vm. No hassles, no headaches.
The problem is trying to install tools built for Linux on Windows.
You're better than me
I didn't mean it that way.
If you have a spare computer, install proxmox on it.
There are loads of tutorials how to do this, it has a good installer, after which it's all a web based GUI.
Use it to spin up VMs to your heart's content, create scripts to automatically provision a new Ubuntu or Debian or whatever flavour. Or run up some Windows VMs. You can pass through GPUs and other devices (tho this can be difficult, again lots of tutorials out there).
Be prepared to spend some time learning proxmox. It took me 2 or 3 installs to figure out the best way to set up networks, storage etc. Mostly cause I just jumped in, found something that could be better, googled that and found a useful tutorial on it so started again.
But once proxmox is running, everything else become so much easier
I don't think proxmox is great if you don't know Linux yet. It's an additional tool to understand. But I do regret not getting into proxmox earlier, since it makes trying new things so much easier.
could you share some tutorials? i'm thinking to rebuild to setup better storage for VMs and backups
That's a pretty broad question.
How many nodes are you running? Are you using CEPH? Or another flavour of distributed storage? Or external nas/san? Or just local arrays? Zfs? Btrfs?
What's your backup strategy? Do you use Proxmox Backup Server?
If you can figure out what you don't like about your current setup, there will probably be a tutorial or article about alternatives.
Sometimes they can be applied without having to reinstall (actually, 99% of them probably can. Sometimes I just find it easier to start from scratch tho)
I've got Docker up and running, but getting anything to work within Docker or getting a machine to access the services that it says are running is a different story
I have worked with Docker/WSL for a number of years and it is more difficult compared to Docker in Linux. There are a lot a unique quirks and bugs that are an absolute pain to deal with.
Would not recommend for any relatively complex use case and certainly not for a server.
This sounds like ports aren't forwarded correctly. At least that's a regular problem I have.
ss -tunlpshows which ports are open and helps me often to find out if I'm just too dumb again ;DI do think that if you continue to set up services on Linux (with or without docker), you'll get quickly to a point where setting up a new service takes only a few minutes.
TECHNICALLY (yes, I'm fun at parties) you need 3 commands, as you also need to do an "apt update" after adding the repo. But we can chain commands of course. Do chained commands count as one? We could debate that for hours. Like why I prefer vi.
My point? None really, just having fun.
You forgot "sudo"! Try again
Joke's on you, I login as root (no I don't, but I do sudo -i instead of each command)
Windows is just not ready for this stuff. Most of this stuff is built for Linux. Linux is THE server OS. And windows is painful for developers too, so there's less solutions for it.
You'll be a lot better off with Linux for self hosting.