We have a handful of ATProto related domains and have had lots of discussion around PDS hosting.
So, let’s learn and document together! Follow this Indie Sky forum, share posts on your current setup and what you want to do.
Learning with Railway
We’ve done a basic install on Railway. Railway supports templates which gives a one click install, and their pricing model is based on usage and this can be quite inexpensive.
We have some work to do here already. The initial install is on my (Boris’) Railway account, and needs to get re-installed on the AT Community Fund account.
Three getting started suggestions on what to do with this install. I would suggest we use this space to coordinate, if there’s lots of code heavy stuff we’ll make a repo at https://github.com/atprotocol-community.
Setup multiple handle domains
And document this
Customize the email templates
And document this
Root install web page
Have something running at the root of the domain https://atprotocol.social - there’s the witchcraft systems stuff, what else?
Different PDS Hosting Approaches
There are of course lots of different hosting types and providers where a PDS can be hosted. Sharing setups & documenting the options would be the goal.
Some other ideas:
- use the
atprotocol.socialinstance for migration testing, test signups, or other flows - fork the bsky PDS Typescript source code and maintain it as a plain docker image rather than the bundle installer
- package the PDS code for other hosting types — eg a Cloudron package
- document & simplify branding and email templates for a PDS (this could be updates to the source code)
- rsky has relatively fewer PDS installs and could also benefit from code contributions and hosting documentation.