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
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.
I followed this guide
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-upgradewould 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
If you're on Debian, it's the tried and true method. The config is dead simple for most upgrades, just un-comment the line in the config file next to the type of upgrades you want, stable or testing. It can take some debugging if you have a package with it's own APT repo. It'll just ignore those updates by default.