docs: add one-click Railway deploy for a hosted relay#2733
Open
hmseeb wants to merge 1 commit into
Open
Conversation
Adds a 'I want my own hosted relay' path to Getting started with a Railway deploy button. The template stands up the relay plus Postgres, Redis and media storage, runs migrations, and generates the owner identity on first boot, so trying Buzz with a real relay no longer requires the from-source path. Flagged as community-maintained, not an official build.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a "I want my own hosted relay" path to Getting started with a one-click Railway deploy button.
Buzz today asks anyone who wants a real relay to take the build-from-source route. This gives non-developers a hosted option: the template provisions the relay plus Postgres, Redis, and media storage, runs migrations, and generates the owner identity on first boot — no configuration.
The listing is flagged community-maintained, not an official Block build, so there's no implied ownership. Happy to adjust wording, placement, or drop the button and keep just a link if you'd prefer.
Template deploys green end-to-end; the owner key is surfaced as a paste-ready
nsec1…in the deploy logs, and one deployment can host multiple communities by hostname.Note: this supersedes the stale #984 — that template modeled a since-removed Typesense service and didn't run migrations.