Because apparently I can’t leave well enough alone. In this post, I’ll dive into how I went about setting up an Nginx reverse proxy for this WordPress site, and some of the challenges I ran into along the way. This was a task that proved to be more challenging than I anticipated, and there were moments that I questioned my ability to get it working. - It’s also got me wondering if my next project should be migrating to a static site generator.
If you’ve been following along with my attempt to migrate this Wordpress site into container services with Podman then you will be happy to know that I’ve achieved the first milestone. The database for this site now resides pleasantly in a rootless Podman container. One of the major reasons I wanted to try Podman was that, outside of installing the package itself, everything I wanted to run could be achieved as a non-root, non-privileged account.
In my previous post about migrating this site to Podman, I laid out a rough outline of my plan to move forward with Podman. Step one was to move the database into a container. I have a few updates on my progress, and some tips to share regarding selinux, and containers that have systemd running for service control. I’ve basically been starting from scratch on this - I don’t have any experience with other container platforms like Docker, I have had some limited exposer to lxd on Ubuntu systems, but I’ve always treated them as live systems – more like a VM than a container.
On occasion I need to pull a host list from Satellite 6; and while using the web ui is often simple enough, the hammer cli that comes with foreman is often faster. Here is a quick way to get a full host list: hammer host list That command will print list of all hosts registered with your Satellite server. Filter by OS major version Often when I’m generating this list it’s because someone has asked me something like: “How many RHEL 5, servers do we have?
Over the weekend I decided it was time to test the in-place upgrade on my Fedora 31 webserver to migrate over to Fedora 32. The process for in-place upgrades on Fedora is a fairly straightforward process and has been flawless ( at least in my experience) over the last few years. If you are thinking about kicking the tires on the new Fedora check out the quick tutorial over at Fedora Magazine to learn how easy it is to perform the upgrade.
Microsoft releases updates on a predictable cadence. The second Tuesday of every month is called “Patch Tuesday”. There aren’t any Linux distributions (that I’m aware of) that have a similar release cadence. Package updates are released pretty much as soon as they are ready. Theoretically, you could check for updates every day and always have new updates to install each day. However, if you have decided for one reason or another to just standardize your Linux patching around Microsoft’s patch release dates, then you will need a good way to figure out when the next Patch Tuesday will occur.