env vars

set from the cli or the dashboard. your choice. both work.

from the terminal

pushto env set DATABASE_URL=postgres://...
pushto env set API_KEY=sk_live_...
pushto env list
pushto env pull    # downloads all vars to .env
pushto env push    # uploads your whole local .env at once
pushto env rm OLD_KEY

rules

keys start with a letter or underscore, then letters, numbers, and underscores. UPPER_SNAKE_CASE (like DATABASE_URL) is the convention, not a requirement. your app reads exactly what you store
values are encrypted before they're stored (aes-256-gcm)
change a value while your app is running and we restart it with the new value. nothing running yet? it rides your next deploy
max 100 vars per project, 10KB per value

vars we create for you

turn on a pushto service and the vars it needs are added for you automatically. zero copy-paste.

dbDATABASE_URL

authPUSHTO_AUTH_PROJECT_ID, PUSHTO_AUTH_URL

vaultPUSHTO_VAULT_URL, PUSHTO_VAULT_KEY

mailPUSHTO_MAIL_API_KEY, PUSHTO_MAIL_URL

from the dashboard

open your project and hit app settings in the sidebar. same encrypted storage, visual key-value editor, bulk import (paste or drop a .env file), and a raw editor when you'd rather type the whole file. the secrets tab is the same storage with the encryption story up front.