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:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
I made a similar post a few weeks ago.
I will try uBlue core and give you all a small update about it.
I feel similar about Debian. It's a good distro for sure and I don't have any issues with it for server use, but somehow, I still don't like it somehow. RPM-/ OSTree based distros are more my taste, and I don't even know why.
I am completely confused about ublue currently, (okay all they did is remove the image list, its the same on Github)
Debian is old and crusty with all its tooling. Apt sucks, automatic updates are strange, there are no snapshots afaik, it uses ext4, its like Fedora was 10 years ago
the only OS to make sense really
How does it make more sense than Fedora KDE?
Because containers (Distrobox, Flatpak, etc.) are bae.
You can read my post I made a while ago for more information: https://feddit.de/post/8234416
Once you "get" image based distros, you probably never want to go back. Traditional distros just feel... off now for me.
Containerisation is the biggest strength in Linux, we use it all the time on servers, so why not on the desktop?
Atomic OSs just make more sense for me, not only because of security/ bug/ whatever reasons, no, also because they feel simpler and are pretty convenient and robust.
I want a server haha.
And yes, atomic ftw.
What makes Debian a pain to use on servers?
Automatic updates are overcomplex and not even preinstalled. Install a package, change some configs, so some more.
I dealt with it and its annoying.
And there is a lot more that is completely manual with no good default presets
unattended-upgrades is annoying? How so?
Its overcomplex. For sure I could get used to it and maybe this is the way to go.
But you could wrap this tedious process in a function.
Fedora has a distro upgrade command (that totally sucks but okay) since many years, while on Debian I needed to follow some random Guide to get on the hyped Debian 12.
Debian releases a migration guide with every new version release. And sorry but if you have trouble updating your system then replacing the source.list file and then updating your system again, you should reconsider running a server yourself, imho.
I was looking for such a guide but could not find it back then.
Which may be overcomplex but it is complete and lots of things where not intuitive at all.
As I said, you could easily automate this step, instead of making it that manual. Or course I can do that, but why need to, if a sudo apt distro-upgrade would do it?
https://wiki.debian.org/DebianUpgrade
Because those steps need manual review. Things change, packages get removed, packages get upgraded, config files need to get manual reviewed and merged etc.
On a simple System without much configuration that stuff does not matter, but when you use different package repositories and backports you need to be careful. I am not sure how introducing a new command does solve those complex issues. Imo only the system admin can decide what the best steps are.
Thanks! Will look into that
cron
run as superuser script.sh
apt get updates
apt get upgrade -y
???
profit?
Why is there apt-get and apt? Also on regular updates there are sometimes package conflicts that need manual configuration. Maybe -y deals with some.
What monstrosity are you running and calling Debian that there are package conflicts on regular updates?
..or, are you talking early-2000's Linux, where SuSe was the only consistent distro and package management hadn't really been fully sorted out?
Probably I got none, just this "do you want to use the maintainers version" which is always a bit confusing. VirtualBox also gave issues but just dont use that crap.
NixOS works really well as an image based server. Use nixos-generate to create a pre-configured image and put it on a flash drive/PXE share, and you're good to go. Automatic updates are a bit confusing and not really documented, but doable. I have code examples.
I would be interested in automatic updates on NixOS!
You can use Fedora IoT which is essentially rpm-ostree based Fedora Server. It would be less confusing if it was just named Fedora Atomic Server.
Omg yes thats true. Thanks!
But CoreOS is also using rpm-ostree, how are they different?
I didn't try CoreOS as I didn't even get how to set it up. As I understand it, it uses a completely different workflow for administering the system compared to regular distros.
Yep, and thats all cloud-first I suppose. It sounds cool but you need to create an ignition file (which sounds very possible) but then you need to get that to a server that doesnt yet have a user account.
I dont understand anything of that. I dont think mounting a drive with that file is possible everywhere, and how do you setup LUKS?
Just no. I see if IOT is actually atomic but normal.
Like, just use a cli installer that can load a file to automate it. Or have a backup user password. There is an issue that addressed this, its old and closed, yeah.