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
cove.town
A PDS, a knot, a spindle, and a hold, atproto infrastructure fully built on itself.
atproto pds self-hosting: some issues and antipatterns | friendmeat
The Bluesky personal data server (pds) repository is weirdly opinionated about stuff that's easy, and unhelpful with the stuff that's hard. They also insist on using a script that installs a whole HTTP server and Docker stack. But if you're gonna use Docker why assume that people don't already have their own stack? It's just weird and annoying. But here's how I did it.
Self-hosting your PDS | jola.dev
How to set up your own atproto Personal Data Server using tranquil-pds and docker compose, walking you through it step by step.
Setting up my own ATProtocol PDS - Blooym
Details of my adventures self-hosting my own ATProtocol Personal Data Server (PDS), including the painful debugging process.
Coves - Community-Driven Forums on atProto
Coves is a forum-like social app built on the AT Protocol. Join communities, share content, and own your data.
Notes on hosting an ATProto PDS on Cloudflare
atproto vancouver (@vancouver.atprotocol.community)
atproto community in Vancouver, Canada Hosted on @commonscomputer.com, a PDS host on a server at @z-space.ca Check out our @blento.app for more info: https://vancouver.atprotocol.community/
Embracing ATProto, part 1: Setting up a PDS
In this series of posts, I'll explore my journey into setting up my workflows and services for atproto. The first step is setting up my PDS. Let's start with a bit of explanation for all this lingo.
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.
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.orgSelf-hosting your own atproto infrastructure is very much attainable and after going through the process, I wanted to do a little series of write ups on how to go about it. Starting with the PDS! jola.dev/posts/self-hosting-your-pds
Self-hosting your PDS
jola.devContinuing the series of atproto self-hosting posts, here's a guide for ATCR and the hold component, an atproto container registry! jola.dev/posts/self-hosting-atproto-co…
Self-hosting an atproto container registry
jola.devI recently got super into the ATProto spec and how different services use PDS to store the data, I put together a quick client-only website that presents all those records in a single, consolidated feed of all my activity: at.diego.codes
at.diego.codes — Diego Vicente
at.diego.codesOk, 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.devPDS Hosting
Resources related to atproto Personal Data Server (PDS) hosting
Bluesky handle directory – PDSes
eny.space
Bitesize Proto: Two PDS containers at the same time; synchronized swimmers - Hitchhiker's Guide to the Atmosphere
