linux@programming.dev
I use Fedora KDE as my homeserver, because it is my media center too. That’s the reason for the desktop.
Cons for me:
First I struggled with firewalld, it is more challenging than UFW. I removed it, because my router does the job.
Second SELinux is very annoying at the beginning. You install samba and vsftp and it will not work until you set permissions for SELinux.
SELinux is complicated for the start. Documentation is not very helpful for this imo. It works now. If you want to have an easy way, you can set it to permissive mode. I kept it running.
Pros for Fedora has actual software and I really love DNF 🥰
Yes you can but you don’t learn a thing from this. A good choice would be permissive mode. You get the warnings, but it works anyway
Selinux policy’s. Its weakness, also its strenght.
I’m using it myself for my vps and it’s fine. I don’t think it’s anything spectacular, but my use case is really basic.
I’m a selfhoster, I setup a home assistant VM and Cosmos Cloud running a bunch of Docker containers, all setup using Cockpit.
Easier, and better looking UI than Proxmox. Also this setup enabled me to use Docker instead of LXD and save on one virtualization layer, which as a beginner every layer adds complexity.
It has been rock solid, it has better hardware support than Debian due to the faster release cycle, only drawback is the lack of documentation or tutorials in comparison to Debian which has a colossal community.
I run Fedora Server on a blade server in a colo.
Pros:
- Cockpit is the GOAT 🐐
- Descended from RHEL so everything is supported
- Podman is the GOAT 🐐
Cons:
- Podman is getting worse, for instance they recently deprecated systemd generate and tell you to use Quadlet, for running pods, you need to use Kubernetes. This greatly complicates my workflow.
- SELinux, while secure, and easy to troubleshoot with Cockpit, is a major pain in the ass that prevents most containers from accessing their data directories. It can be corrected but is extremely frustrating.
- Quadlet is extremely inconsistent, I can copy the working unit file for a container and it works, change the name and variables for another container, and one launches but the other won’t start. One will have the wrong name. Stupid things, like putting the name in quotes, reloading, removing the quotes fixes it. I have harsh words for the idiot who deprecated systemd generate.
- something like Tiddlywiki, their documentation will put you in /var/www but Fedora uses /usr/www or something. You get used to the Fedora things but you can end up on a goose chase sometimes.
Those cons are starting to hit hard, and when I reimage this server next I’m probably going to Proxmox or Debian. Server 37 was good but I probably won’t bother with 39.
Fedora uses /var/www. Dunno what gonk you read or told you otherwise. There’s SELinux policies built in for that directory. You probably are confusing the default html files at /usr/share/html. These are separated intentionally. The /usr/share/html directory is managed by RPM, the other /var/www is content designated as web server files.
