Self-hosting Wafrn behind another Caddy, with BlueSky support
I’ve wanted to self-host a way to post in one place and reach BlueSky, Mastodon, Lemmy, etc… for a while. Wafrn is it, but hosting can be fussy. Here’s what I did.
The recommended deployment is probably easy; it’s just a Docker container, and if given a whole server, or at least control of the whole web frontend there shouldn’t be much to it. I wanted to run it on my existing VPS, which has a bunch of services running behind Nginx. The deployment instructions explain why that won’t work easily; Wafrn relies on Caddy’s automatic HTTPS for ATProto accounts.
Using the Caddy from Wafrn’s container as a proxy is an option, but I really wanted the main web server to be separate. Fortunately, I had nothing against Caddy itself, and converting the Nginx config was a one-shot for an LLM tool.
Updating Wafrn to run in that configuration was not. I did use such a tool in that process, though it made enough errors along the way I think I may have been faster without it. I put the resulting fork up on Gitlab in case anyone else wants to do the same.
@fediverse
@fediverse@lemmy.world
#wafrn #atproto #bluesky #fediverse #blog
