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.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | blog.goodanser.com |
| Canonical URL | https://blog.goodanser.com/fediverse/post/03c6a4f4-cdd4-4027-a6a4-5017dd9154bd |
| Publication time | Tue, 26 May 2026 03:18:15 +0000 |
| Retrieval time | 2026-05-26T03:37:43.011Z |
| Last seen | 2026-05-26T03:37:43.011Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | ANNDAV_QQTCy |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
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
