diff --git a/packages/docs/docs/getting-started/deployment/railway.md b/packages/docs/docs/getting-started/deployment/railway.md index 2391d1f..79046c5 100644 --- a/packages/docs/docs/getting-started/deployment/railway.md +++ b/packages/docs/docs/getting-started/deployment/railway.md @@ -1,6 +1,6 @@ # Deploy on Railway -The fastest way to get HappyView running is with Railway. This template deploys HappyView and Postgres with a single click: +The fastest way to get HappyView running is with Railway. Choose the database you want and these templates will deploy HappyView with a single click: | SQLite | PostgreSQL | | --------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | @@ -16,12 +16,18 @@ After deploying the template, you'll need to configure a few things before the s openssl rand -base64 48 ``` -2. **Assign a public domain.** In the Railway dashboard, add a public domain to the HappyView service. The service needs a publicly accessible URL for OAuth callbacks. Set `PUBLIC_URL` to this domain (e.g. `https://happyview-production.up.railway.app`). +2. **Set your token encryption secret.** In the HappyView service variables, `TOKEN_ENCRYPTION_KEY` must be a Base64-encoded 32-byte key. This is used for encrypting plugin secrets and DPoP private keys at rest. + + ```sh + openssl rand -base64 32 + ``` + +3. **Assign a public domain.** In the Railway dashboard, add a public domain to the HappyView service. The service needs a publicly accessible URL for OAuth callbacks. Set `PUBLIC_URL` to this domain (e.g. `https://happyview-production.up.railway.app`). :::note Your instance can use a custom domain or Railway's generated URL with no additional configuration. ::: -3. Access your HappyView dashboard at the instance's public URL. The first user to log in is automatically bootstrapped as the super user. +4. Access your HappyView dashboard at the instance's public URL. The first user to log in is automatically bootstrapped as the super user. ## Next steps