I definitely do not hate SELinux, I think it’s a great system. But my experience mostly (at home, anyway) comes from managing servers running Kubernetes clusters and, like, just using podman do deploy containers. In both these cases SELinux is a on “just works” basis, for the most part.

Then in enterprise environment that doesn’t run everything on containers, you usually have a very standardized way of applying SELinux policies. At my last place of work we did it via a rather Ansible role. It was simple and easy.

But I can imagine using SELinux at home, where you maybe don’t have these things, might be a rather “mysterious” experience. It’s not the most obvious system.

But learning to write your own policies (even if just trough se2allow or whatever it’s called) does de-mystify SELinix pretty quick.

If Fedora wants to promote FOSS then it would make sense to just have it’s users enable Flathub if they want to. Instead of outright promote a repository that promotes proprietary software.

If you meant it as moral question, then then answer would probably be that proprietary software does’nt guarantee the same user freedoms as free software. And thus does’nt let users control the software that runs on their own computers.

Oh yeah, that makes sense. Thanks for the info. I was under the impression that Flathub was a default flatpak repo in Fedora anyway.

But yes, always with these trade-offs. It’s bad when package maintainers package software, and it’s bad when software developers package software…

Why is Fedora packaging their own flatpak of OBS in the first place, when a seemingly working, official one is available on Flathub?

Great decision! Not only does this make Tumbleweed match MicroOS better, but also the RHEL-based distros. SELinux is not super obvious to use, of course, but I’ve never understood how AppArmor works.

Ubuntu doesn’t allow pip to install system wide stuff anymore. You can solve that by installing everything in a pyhton virtual environment.

But for real, use Docker/Podman instead. It’s a lot easier, especially if you’re managing several applications!

The Beeline is definitely powerful enough to run a hypervisor, so I would do that if I were you. Proxmox is a very good product and easy enough to use. Personally I use Harvester (with Rancher) but that might be a bit daunting if you’ve not used Kubernetes before.

I would recommend running Proxmox as your OS, spin up a few Debian virtual machines and run your services (Nextcloud, plex/jellyfin, …) with Docker containers. I would personally use Podman, as I think it’s the simpler one to use, but there might be more documentation online for Docker, I’m not sure. But do definitely use containers! You’ll thank yourself in 6 months.

For reverse proxy I would suggest using Traefik, especially is your using Docker/Podman. But there are other good solutions like Nginx Proxy Manager, which has the advantage of being very easy to use. But I do run Traefik on every Podman server I have or any Kubernetes cluster. That way I can just have a wildcard DNS entry for an IP and then every proxy route will just work, whitout having to touch the DNS further.

Also, just a general tip: look into how you can deploy everything using a GitOps flow. Whether that just be with Ansible or more specialized solutions (Kubernetes with ArgoCD or FluxCD is very well suited for this). Look into Terraform/OpenTofu. This last point is nowhere necessary, but if you ever (like me) get tired of forgetting how you setup your infrastructure (virtual machines, application deployments and configuration, etc) you’ll love GitOps.

Oh, but do definitely look into Ansible for configuring your servers. It will save you a lot of time in the long run.

I’ve completely switched from cron to systemd timers for everything. I feel like they are a lot easier to remember and keep track of! Plus, getting logs for free is pretty nice as well

Windows 11, and the group policies doesn’t allow us to use WSL. We also can’t directly SSH into any servers so we have to go trough a Citrix session to a Windows 10 “admin server” and then SSH or RDP to a Linux server. And Windows Terminal isn’t installed on the Windows 10 server, so it’s either CMD or the Powershell terminal.

It’s absolutely fucking miserable. I’m a Linux sysadmin who do a lot of automation (ansible etc) but also Python development. Try it yourselves and see how long you last! I’m jumping the fucking ship in a month though, thank the gods.

All the result of an over confident “security organization”, with a lot of hubris.

But the best part? It’s a $5000 work laptop, and my 6 year old Thinkpad (with Linux) runs laps around the thing any day of the week. Opening the file explorer takes, most of the time, 5+ seconds…

Fuck my life, and fuck this company.

I think that’s kind of what they meant. I’ve also selfhosted Nextcloud for years, but I only use file sync and calendar/contacts.

Lately I’ve been feeling that Nextcloud is too big and clunky for just that. Like it’s something I’d love to setup at work or for an org, but that it “feels” to heavy for home use these days.

I need to check out Radicale, I think.

My dream would for this to at least have an option for collapsable tree-style tabs. That’s what I’m missing the most from the Edge implementation. Even “normal” vertical tabs struggle when you have over a hundred open tabs.

Yesss come on! I moved to Edge at my place of work because I can no longer see what I’m doing with horizontal tabs. And we can’t use addons in Firefox.

This will land in ESR in three years time and then we’ll be rolling…

I set lower priorites (higher number) for all repos from OBS and such. The only repo that has a higher priority is Packman. You can see your priorities with “zypper lr -p”, and set priorities with " zypper mr -p 100 <repo-id>".

Same thing happened to me. I just continued on and changed TTY and all was fine.

OpenSUSE MicroOS or Fedora CoreOS. If you’ll be using containers you’ll have a great time. If you don’t want to deal with transactional systems, then there is literally nothing I’d rather use than Debian.

Writing systemd services for your containers is something yoully have to get used to with podman, pretty much. It’s actually very easy with the built in command “podman generate systemd”, so you can just do something like " podman generate systemd --name my-container > /etc/systemd/system". I much prefer managing my containers with systemd over the docker daemon. It’s nice!

Also, podman can use privileged ports as root, right?