openpgp4fpr:74EDD2488126072A9E9FD0C7348F97E620E0BA7A

  • 0 Posts
  • 17 Comments
Joined 6 months ago
cake
Cake day: February 11th, 2024

help-circle


  • tekeous@usenet.loltoSelfhosted@lemmy.worldConfused about Podman
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    6
    ·
    18 days ago

    My major beef is we used to be able to run a Podman generate command to make a user systemd file and auto start and stop containers with that. Even entire clusters of pods with one easy command and then just use the system level start and stop. They removed it in favor of “quadlet”which works fine for single containers, but for a compose, they literally just use Kubernetes syntax and the official documentation says just use Kubernetes. Well, what the fuck is Podman for then?

    The biggest problem everyone ever has with Podman is it’s frustratingly obedient to SELinux. Docker just kind of makes its own permissions and opens its own ports and steamrolls past whatever security you have. Podman will refuse to read or write a directory for stupid reasons until you’ve gone round and round with SELinux, and then just when you have it working, when the container updates it locks the directory all over again(in my case, updating a Minecraft server to latest version would crash the server and lock the data directory). Red Hat continues to insist SELinux is cool and this is working as intended. Again, Docker just doesn’t give a shit and barges into the directory without a problem.


  • tekeous@usenet.loltoSelfhosted@lemmy.worldConfused about Podman
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    8
    ·
    edit-2
    18 days ago

    Podman is quickly becoming shit as Red Hat continues to remove features and recommend you use Kubernetes. I ended up removing it from my servers and switching to Debian from Fedora because I don’t like Red Hat mucking about with our open source community software.

    I still run Docker.









  • Set up Paperless-ng on your server, generally with Docker, and map the Consume folder to wherever you want. Expose that on the network as a Samba or FTP share depending on your printer.

    Printers with a bit more than basic features allow you to “scan to target” and it’s basically designed to set up a Public share folder on windows and scan and your document just shows up on the computer. Same deal but map it to the consume folder on the server. Paperless automatically picks up and intakes anything dropped in the consume folder.

    So you end up just hitting Scan on the printer, the printer will dump the output into consume share via either samba or ftp, and Paperless automatically picks it up and puts it in the Inbox for ya.


  • tekeous@usenet.loltoLinux@lemmy.mlDocument Management System for Linux?
    link
    fedilink
    English
    arrow-up
    10
    arrow-down
    1
    ·
    9 months ago

    I use Paperless-ng and it’s great. Headlining feature is that it stores your documents in PDF in a plain folder which makes backing up easy. Another software that puts your documents in a database is no good unless it has its own backup method.

    Plus being on a network server means I can set up my printer to scan to there as a target, my phone to scan to there, computer, I can drop emails in the consume folder, etc. Easy peasy to get stuff in there.


  • 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.



  • To answer your question about lack of dock and system tray, I use the top left hot corner to snap windows in Activities often, and I launch mostly from the built in Applications menu. Don’t use the dock much. As for system tray, it’s a fairly minimal work computer so I boot it every day, run slack, browser, etc. and I know there’s nothing really on the background. Don’t need an icon for slack, it’s always on my screen. In my GNOME-based work environment it’s either running and I can see it or it’s closed.


  • I’m using pure GNOME with the exception of a single extension which tiles windows on my screen on a grid(gTile) because I have a massive screen and five windows. I also have an icon pack if you’re counting that. Rest of it is stock and I quite like it. It gets out of my way when I’m trying to work and the alt+tab and other features are always fast. Top left hot corner is a godsend.