Nah @exu is right: non-IT focused companies do not have the skills or desire to reliably set up and maintain these systems. There is no benefit to them creating their own server stack based on a community distro to save a few bucks.

Smaller companies will hire MSPs to get them setup and maintain what they need. And medium to large size companies would want an enterprise solution (IE: RHEL) they can reliably integrate into their operations.

This is for a few high value reasons. Taking Red Hat as an example:

1. Standardization (IE: they can hire people with RedHat certificates and they will be a few steps ahead in ramping up to internal systems)
2. Vendor support (IE: if something critical isn’t working they can get quick support from a Red Hat technician and get it resolved quickly)
3. Reliability (IE: all software is backed and tested by Red Hat and if anything breaks from a package update its on Red Hat to fix)

When lots of money is on the line companies want as many safety/contingency plans as they can get which is why RedHat makes sense.

The only companies that will roll their own solution are either very small with knowledgeable IT people (smaller startups), or MASSIVE companies that will create very custom solutions and then train their own IT operations divisions (talking like Apple, Microsoft, Amazon levels).

Not to say what Red Hat did is justified or good, because hampering the FOSS ecosystem is destructive overall, but just putting this into context.

Yeah, management positions are often filled by people who:

A) Want to get a higher paying job and don’t care about the product or the industry necessarily (MBA-circlejerk types).

B) Are Devs/Artists/Creatives that wanted increased compensation, and the only way up was as a manager where they have less aptitude.

Executive staff needs to better integrate management as “servant leaders” within teams, and compensate EVERYONE better

I’ve been checking for the Flatpak daily 😭

This is where you can track the issue

Another shitty thing about Plexamp is there is no easy way to download your entire library in a converted format and auto download any new additions.

The developer said that “this is not the intended use of Plexamp”, but the reasoning is flawed IMO

The only thing keeping me on Plex is iOS downloads supported natively.

The second Swiftfin gets that I will be switching fully to Jellyfin

Unless Plex adds something new and exciting that pushes them beyond FOSS offerings

For anyone looking for a chair that doesn’t want to spend >$1000 or get a gaming chair, I recommend looking for an office furniture reseller in your area.

There are a lot of shops that buy used furniture from companies either going out of business or moving.

I was able to get a new Steelcase for like half the price, still had its tags and packaging. Granted this was during covid where a lot of businesses were dumping their in-office supplies, but still worth a look.

Restic and borg are the best I’ve tried for remote, encrypted backups.

I personally use Restic for my remote backups and rsync for my local.

Restic beats out borg for me because there are a lot more compatible storage options.

Yeah I saw a post about it a long time ago on Reddit for users with lots of devices

Basically it is just setting up one or two “central devices” that know all the client devices, but not linking the client devices individually.

IE: One server is connected to your phone, laptop, tablet, desktop, etc. But the phone is not directly connected to your laptop or desktop or tablet.

To be fair I don’t actually know if this is the best approach anymore or if just connecting all of them in a mesh is better 🤷

Here is a forum post describing it.

Plex, PiHole, Photoprism, Home Assistant, Syncthing in a hub and spoke config, Caddy for reverse proxy, custom containers for: yt-dlp, restic, and rsync.

I bought a .com for like $10 CAD from Cloudflare that uses a URL not linked to me.

Maybe overly paranoid, but it also makes it easy to get SSL certificates for my lab.

From a user perspective, Distrobox is a tool that lets you “spin up any distro inside your terminal”.

You can basically create a mini Linux environment of any distro that you can access through the terminal. You can set it to share your home folder, our create a new home folder just for that mini environment.

Behind the scenes Distrobox is creating and managing containers through Podman or Docker. You could technically achieve the same thing by manually setting up Podman containers, Distrobox just makes it very easy to create and maintain those containers with the correct permissions. It also has useful tools where you could install an app in a Distrobox container, but then add that app to your host OS app list.

This makes it especially useful for immutable OSs. Instead of adding packages to your base OS, which should be kept as minimal as possible, you can just install them in a Distrobox, so your host’s root filesystem is unaffected.

I run everything in rootless containers using systemd service files generated with podman generate systemd.

Podman Compose is a “community effort”, and Red Hat seems to be less focused on its development (here is their post about it).

There are ways to get it working but I find it easier to go with podman containers and pods through systemd because the majority of documentation (both official and unofficial) leans in that direction.

I don’t know how much you already know, so here is just a summary of things that worked for me for anyone reading.

Podman uses the concept of “Pods” to link together associated containers and manage name spaces, networking, etc. The high level summary for running podman pods through systemd:

• Create an empty pod podman pod create --name=<mypod>.
• Start containers using podman run --pod=<mypod> ... and reconfigure until containers are working within the same pod as desired.
• Use podman generate systemd to create a set of systemd unit files. Be sure to read through the options in that man page. – this is more reliable than creating systemd unit files by hand because it creates unit files optimized for the podman workflow.
• place the generated systemd unit files in the right place (user vs. system) and then it can be started, enabled, and disabled as with other systemd unit files.

Note: for standalone containers that are not linked or reliant on other containers, you can should skip creating the empty pod and can skip the --pod=<mypod> when starting containers. This should result in a single service file generated and that container will operate independently.

This post goes over pods as systemd services.

This doc goes over containers as systemd services.

The Red Hat Enterprise Linux docs have a good amount of info, as well as their “sysadmin” series of posts.

Here are some harder to find things I’ve had to hunt down that might help with troubleshooting:

• Important: be sure to enable loginctl enable-linger <username> or else rootless pods/containers will stop when you log out of that session.
• If you want it to run a container or pod at system startup you will need to specify the right parameters in the [Install] section of the systemd file, see this doc page. Podman generate systemd should take care of this.
• If you are using SELinux there is a package called container-selinux that has some useful booleans that can help with specific policies (container-use-devices is a good one if your container needs access to a GPU or similar). Link to repo