Platform variables
Every variable Deplo itself reads, to configure the platform.
These configure the platform. For variables your apps read at runtime, see Environment variables.
Control-plane variables
Read by the panel container. install.sh sets them in /opt/deplo/docker-compose.yml.
Prop
Type
More on DEPLO_TAKEOVER in Migrations, on DO_NOT_TRACK in
Anonymous usage statistics.
Variables read by install.sh
Set them in front of the command, like
curl -fsSL https://deplo.build/install.sh | DEPLO_DOMAIN=deplo.example.com bash.
Prop
Type
DEPLO_SECRET, DEPLO_DB_PASSWORD, DEPLO_HOST_BOOTSTRAP_TOKEN and DEPLO_SETUP_KEY are
not read from your shell: the installer generates them into /opt/deplo/.env (mode 0600)
on the first run and never rotates them.
Variables read by install-agent.sh
Set after sudo, which drops the caller's environment. The dashboard command already does it
for the role flags. See Server roles for what each role changes.
Prop
Type
Before you change one
DEPLO_SECRET is permanent
Back up /opt/deplo/.env. See Disaster recovery.
DEPLO_SERVER_IPmust be a real, internet-reachable address. Generated hostnames encode an IPv4 in hexadecimal and an IPv6 afterv6-, so a private or loopback address produces URLs that only work from that machine.- A custom domain in
DEPLO_PUBLIC_URLcarries no IP, so Deplo falls through to interface detection. SetDEPLO_SERVER_IPexplicitly on a multi-homed box. - Build-time placeholders in the Dockerfile (database URL, secret) never reach the runtime image and are not usable values.
See also
Did this page help you?