Selfhosted

39158 readers

404 users here now

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!

founded 1 year ago

MODERATORS

[email protected]

Do you run an image-based Server? (feddit.de)

submitted 6 months ago by [email protected] to c/[email protected]

35 comments fedilink hide all child comments

I use Fedora Kinoite daily and find it to be the only OS to make sense really.

I find Fedora CoreOS totally confusing (with that ignition file, no anaconda, no user password by default, like how would I set this up anywhere I dont have filesystem access to?)

But there are alternatives. I would like to build my own hardened Fedora server image that can be deployed anywhere (i.e. any PC to turn into a secure and easy out-of-the-box server).

As modern server often uses containers anyways, I think an atomic server only makes sense, as damn Debian is just a pain to use.

Experiences, recommendations?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 16 points 6 months ago (13 children)

What makes Debian a pain to use on servers?

[+] [email protected] -13 points 6 months ago (12 children)

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

[+] [email protected] 3 points 6 months ago* (last edited 3 months ago) (1 children)

[removed by mod]

[–] [email protected] -1 points 6 months ago (2 children)

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.

[–] [email protected] 3 points 6 months ago (1 children)

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.

[–] [email protected] -1 points 6 months ago (1 children)

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-upgrade would do it?

[–] [email protected] 3 points 6 months ago (1 children)

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.

[–] [email protected] 1 points 6 months ago

Thanks! Will look into that

load more comments (10 replies)