Self-hosting Wafrn behind another Caddy, with Bluesky support
The article discusses the author's experience self-hosting Wafrn to post on platforms like BlueSky and Mastodon. It highlights the challenges of deploying Wafrn behind an existing Nginx server and the need for Caddy's automatic HTTPS support. The author shares their solution and offers a fork of the project on Gitlab for others to use.
- ▪The author wanted to self-host a way to post on multiple platforms including BlueSky and Mastodon.
- ▪Wafrn requires Caddy's automatic HTTPS, complicating deployment behind an existing Nginx server.
- ▪The author created a fork of Wafrn and shared it on Gitlab for others to utilize.
Opening excerpt (first ~120 words) tap to expand
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.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at blog.goodanser.com.
Discussion
0 commentsMore from blog.goodanser.com
