Railway
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:
Required configuration
After deploying the template, you'll need to configure a few things before the stack works properly:
-
Set your session secret. In the HappyView service variables, set
SESSION_SECRETto a random string of at least 64 characters. This is used to sign session cookies.openssl rand -base64 48 -
Set your token encryption secret. In the HappyView service variables,
TOKEN_ENCRYPTION_KEYmust be a Base64-encoded 32-byte key. This is used for encrypting plugin secrets and DPoP private keys at rest.openssl rand -base64 32 -
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_URLto 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. ::: -
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
- Configuration — full list of environment variables
- Dashboard — manage lexicons, users, and plugins via the web UI
- Production deployment — hardening checklist for production instances