search

bluesky-social / pds

Bluesky PDS (Personal Data Server) container image, compose file, and documentation
Other
714 stars 60 forks source link

Multi-protocol routing options #30

Closed HelloFillip closed 4 months ago

HelloFillip commented 5 months ago

I currently have several data solutions operating at the root of my domain, including ActivityStreams / ActivityPub, Solid, and now ATP. The goal is to enable a reverse proxy to route to the appropriate service based on the request content (essentially URL pattern and headers).

Are there recommended methods of defining this separation to route requests to the PDS appropriately?

bnewbold commented 5 months ago

Currently, almost all atproto routes have the prefix /xrpc/, and it should be pretty easy to configure nginx (or other web servers) to route just those requests to a PDS implementation.

It is conceivable that this prefix could change in the future; we don't use the term "XRPC" much any more, as it is a bit confusing. In short we aren't promising that this routing will work forever. But it should work for now.

Jacob2161 commented 4 months ago

The /xrpc/ prefix is very unlikely to ever change, so should be safe to forward explicitly.