Ok, continuing the series on the atproto self-hosted components that make up covetown, here's how you set up a knot and spindle for @tangled.org Caveat: they're in the process of rolling out new components, but there's a migration path, and I'll write about that too! jola.dev/posts/self-hosting-and-tangle…
Self-hosting and Tangled
jola.devAug 20, 2026 at 12:18 PM
cove.town/cove.town
Self-contained atproto self-hosting setup with PDS, knot, spindle, and hold
cove.town/cove.town
Self-contained atproto self-hosting setup with PDS, knot, spindle, and hold
Migrating to the new Tangled knot2 | jola.dev
Tangled is a Github alternative built on atproto. I've previously shown you how to set up the self-hosted repo server, here I go through migrating to knot2.
cove.town
A PDS, a knot, a spindle, and a hold, atproto infrastructure fully built on itself.
treybastian.com/tangled-spindle - ATCR
Container image treybastian.com/tangled-spindle on ATCR
ahhhh it works! I have an atproto PDS, knot, spindle, and hold, all driven by a repo hosted on the knot, running on container images created by the spindle and hosted on the hold. The accounts that tie it together all live on the PDS. tangled.org/cove.town/cove.town
cove.town/cove.town
tangled.orgalright tanglers, it's back to shipping 🛳️ 🌐 Tangled Sites is here: serve websites straight from your repo. grab your `tngl.io` domain at tangled.org/settings/sites. already have a `tngl.sh` handle? that's your domain—ready to go! 📄 docs.tangled.org/hosting-websites-on-tangled.h…
