Custom Environment Variables

On a self-hosted instance, a worker’s process environment can be extended with custom variables that apply to the scripts it runs. This matters for code that reads an environment variable before your script’s entry point even runs — a Go package doing configuration in its init() function is the typical case, since by the time main() starts it’s too late to inject anything.

Add one entry per line, one KEY=VALUE pair per entry:

<KEY>=<VALUE>

<KEY> is the variable name as the script’s runtime will see it; <VALUE> is set verbatim.

These only apply to deployed runs — the script’s own Test / preview run does not receive them, so if a preview behaves differently from a deployed run, a missing custom env variable is a likely reason why.