Self-hosting and Tangled

Following the blog post on how to self-host a PDS (Personal Data Server) for atproto, having your accounts live on your own server, while still being able to interact with apps like Bluesky and pckt.blog, I wanted to write a little about how to do the same for Tangled. Caveat: the Tangled team are working on a new generation of components, including knot2, mill, and the new appview based on bobbin. There will be some form of migration path, but it's all in active development. Tangled is basically Github on atproto. In other words, Tangled offers repo hosting, CI actions, and social coding features. Where they differ is that Tangled doesn’t have private repos yet (we’re all waiting with baited breath for permissioned data to land), and that Tangled allows you to self-host your infrastructure while still participating in the social features. If you’re hosting a forgejo or gitea instance, or have been thinking about it, this is really the killer feature. The other self-hosted Github…