I containerized my homebrew web app
Many years ago, I wrote a Laravel app that helps me track my workouts. Many commercial services did not (and still do not) allow me to enter some information that I consider relevant, so when I switched to a job that required some Laravel knowledge, I wrote this logging app that allows me to import Strava workouts and add my own stuff to them.
Last weekend I switched Linux distributions on my main laptop (Tuxedo OS to Fedora - huge improvement). One last job that I still needed to do, was to migrate my web app.
On Tuxedo OS, I had simply installed Apache, MariaDB and PHP. This time, I wanted to containerize the app in order to reduce the number of running services.
I had some trouble with SELinux. The containers started fine, but refused to read my configuration files. I also had some trouble with Podman not playing nice with my compose.yaml file, so for now, I simply use Docker.
To my mild suprise, the container feels snappier than my previous setup.
8 replies
I thought this was going to be about making beer in your garage. I didn't really understand anything under the title, but congratulations! I think.
I do have a brewing kettle in my garage, but that is not dull. Brewing beer is fun.
I, as well, am here for the garage beer.
Lemmy, the place where a title could go either way
Thought this post was gonna be about using Homebrew
brew🙃Universal Blue projects have integrated Podman/Distrobox/Brew/Bazaar installed out of the box.
Compared to normal Fedora/Silverblue/Kinoite.
Spiffy!
Which Fedora did you install?
I've been using Silverblue, but am having issues with system updates, where it hangs, fails, reverts (the coolest part about being Immutable), then repeats 2 or 3 times before finally succeeding.
44, KDE edition.
What options / syntax in your compose did podman not like?