• @[email protected]
    link
    fedilink
    English
    127 months ago

    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.

    • @[email protected]
      link
      fedilink
      47 months ago

      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.

    • IdiocyOP
      link
      07 months ago

      Thanks for sharing it in details. Very helpful.