SpocketDOCS
DEPLOYING

Environment variables

Tokens, connection strings, and anything else that should not be in your code.

Setting a value

TEXT
Set DATABASE_URL on price-scraper to postgres://… and restart it.

Values are encrypted before storage. Setting one restarts the app by default, because a running process does not pick up a new value on its own.

If setting a variable reports that the machine will not take it, the app is running on one built before this was supported. Deploy it again and the values are applied.

Why you cannot read them back

There is no way to retrieve a stored value — through the panel, through the API, or through a connected agent. Only replacement.

This is a deliberate limit rather than a missing feature. An agent with access to your account is a useful thing; an agent that can read every secret you own out of that account is a liability. Write-only keeps the first without the second.

Keep your own copy of anything you cannot regenerate. We can tell you a variable exists; we cannot tell you what is in it.

Names we recognise

VARIABLEUSED BY
DISCORD_TOKENDiscord apps
BOT_TOKENTelegram apps
TWITCH_TOKENTwitch apps

Any other name works too — these are just the ones our templates expect. Your code decides what it reads.

There is no list to register a name on. A variable your app has never had before is applied exactly like one it already uses, on a running app, without redeploying.

PREVIOUSDeployingNEXTLogs and status