This maybe isn’t for everyone but I de-dockerified Shlink pretty quickly. Moving it to two nginx vhosts (server and admin) on a Shlink LXC and a centralized Postgres server made dealing with it a lot easier.
E.g., the initial API key shenanigans were less fiddly after I took more direct control.
After a long career in tech, one of the things I start to push for when I inevitably take over ops at my new job is to eliminate the silly names.
I don’t do it because I hate fun, I do it because when someone yells, “Squirtle has dropped off the network!” I don’t want to have to go consult a lookup table to learn that Squirtle is a staging environment postgres replica and not the primary billing database.
As a result, I apply the same standards to my home network without shame.
It was mostly uneventful, to be honest. I downloaded the two apps (static admin and the php app), tossed them into /opt/www, and set up nginx to serve PHP. The config in the main app had a section for my Postgres settings and the docs gave the instructions on putting the default server configuration into the static site.
The only challenge was actually rather silly: I don’t use PHP so it took me a bit to understand why apt install php installed Apache when I had already installed nginx. Once I found php-fpm it was smooth sailing from there.