Runtime
Environment variables
What your server code finds in env.
Set by Inhaus
| Name | Example | What it is |
|---|---|---|
INHAUS_APP_ID | app_01J9X2… | The app's id. |
INHAUS_WORKSPACE_ID | ws_acme | The workspace's id. |
INHAUS_VERSION | 7 | The version that is running. |
INHAUS_APP_URL | https://lead-tracker--acme.inhaus.dev | The app's address. |
INHAUS_API_URL | https://inhaus.dev/api/v1 | Used by the SDK. |
INHAUS_APP_TOKEN | (secret) | The app's own token, used by the SDK for files. Never send it to the browser. |
INHAUS_DB_SCHEMA | app_01j9x2… | The name of the app's database schema. |
INHAUS_GATEWAY_PUBLIC_KEY | (PEM) | Verifies the signed-in user header. See getUser. |
Names starting with INHAUS_ are reserved. You cannot set or overwrite them.
Your secrets
Every secret you set is in env under its name, for example env.HUBSPOT_TOKEN. Changes apply from the next request, with no redeploy.
In the browser
Browser code has no env. Anything a page needs at runtime should come from your server code or from getUser().