Guides
Environment variables
Variables are encrypted at rest and layered across three scopes — workspace → project → service — with later scopes overriding earlier ones. Each variable is typed (plain, secret, generated, or reference) and can apply to build, runtime, or both.
Bulk editing
- Import .env — paste a whole .env blob or load a file; comments, quotes,
exportprefixes, and multiline values are handled. Available on service, project, and workspace editors. - Edit as .env file — the service editor can flip into a full-file mode showing every variable (secrets revealed after an audit-logged request). Edit freely; removing a line deletes that variable.
Variable types
| Type | Behavior |
|---|---|
| Secret | Encrypted, write-only in the normal editor (shown as ••••••). |
| Plain | Readable in the editor — for non-sensitive config. |
| Generated | HostRails mints a strong random value server-side. |
| Reference | Points at another variable, e.g. ${{project.DB_URL}} — resolved at deploy time, so consumers stay correct when the source changes. |
Database URLs, automatically
Provisioning a database injects a project-level connection variable (a service named db yields DB_URL). Apps in the project inherit it with no copy-pasting of credentials.
Redeploy semantics
Saving changed variables marks running services needs redeploy; tick Redeploy after saving to rebuild immediately.