I started thinking about what I would need to do to use Aurora as both a server and desktop at the same time. It seems there are server components available in Homebrew, like Samba, that are also available as packages from Fedora if I forked Aurora and added the package to my own custom image.
I don’t mind forking, in fact it’s something I want to do because it interests me, but loading it via Homebrew means I wouldn’t have to maintain my own fork.
So which approach is preferred by uBlue? Jorge seems to like Homebrew a lot (and so do I). When packages are available in both Fedora and Homebrew for something like Samba, which method is preferred by uBlue?
Edit: 11/1: Well, ignorance is bliss, or maybe not in this circumstance. Samba is already installed on Aurora. IDK why that had not occured to me. I still wonder though about linuxbrew vs modifying the image for server stuff.
I haven’t seen Jorge’s talk, but my approach has largely been to run server components as Podman containers running as systemd services using quadlet. This allows you to keep the server software separate and isolated from the rest of the system installation (which can be more oriented towards desktop/workstation use). It also enables you to use server software from whatever source you like (be that the Fedora repos, or perhaps Ubuntu/Debian ones, or even Homebrew or straight from the source).
For something like Samba, you could install the Samba software inside a container, and then bind mount whatever directories you want to share, and then expose the TCP/UDP ports needed for Samba on the host.
I actually looked into that, but I don’t think there’s any official version of Samba in a Docker container, only community versions. If at all possible, I’d like to run it in a way that’s officially supported. Of course, I don’t know if Homebrew qualifies in that regard, but Fedora’s package certainly does.
