From feedd70e08f68a2627f6d9d9ef5666c8eeb90464 Mon Sep 17 00:00:00 2001 From: Haseeb Azhar Date: Fri, 24 Jul 2026 22:25:24 +0500 Subject: [PATCH] docs: add one-click Railway deploy for a hosted relay 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. --- README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/README.md b/README.md index 6aa3eeff0b..d3f90537b8 100644 --- a/README.md +++ b/README.md @@ -119,6 +119,14 @@ Grab a packaged build from the [latest release](https://github.com/block/buzz/re By default the app connects to `ws://localhost:3000`. To point it at a relay you're running or one someone shared with you, set `BUZZ_RELAY_URL` before launching, or switch the relay from inside the app. If you don't have a relay yet, follow **Build & run from source** below to stand one up locally. +### I want my own hosted relay + +To run a relay for your team without managing servers, deploy one to Railway in a click: + +[![Deploy on Railway](https://railway.com/button.svg)](https://railway.com/deploy/buzz) + +It provisions the relay with Postgres, Redis, and media storage, migrates the database, and generates your owner identity on first boot — no configuration. The deploy logs print an `nsec1…` key; choose **Use an existing key** in the app, paste it, and point the app at `wss://.up.railway.app`. One deployment can host several communities. (Community-maintained template; not an official Block build.) + ### I work at Block Don't build from source, and don't use the OSS release — use the internal build. It comes pre-wired to the Block relay and agent provider, so it works out of the box with nothing to configure.