Repository navigation
Environment variables and secrets
Luthfi Yufajjiru edited this page Oct 27, 2026
·
1 revision
sudo morrow set-env api LOG_LEVEL=info PORT=8080 # plain values
sudo morrow set-env api DB_PASSWORD:s=hunter2 # :s = secured (encrypted)
sudo morrow set-env --secured api API_KEY=abc STRIPE_KEY=xyz # --secured = all secured...
sudo morrow set-env --secured api DEBUG:u=false # ...except :u (unsecured)
morrow list-env api # secured values show as **** unless you can read the key
sudo morrow get-env api DB_PASSWORD
sudo morrow del-env api PORT
# One-off values for a single start; not saved
sudo morrow start api -e FEATURE_FLAG=on -e LOG_LEVEL=debugChanges take effect on the next start/restart.
How secured values are protected. They are encrypted with AES-256-GCM using the master key. Whoever can read the key file can decrypt them: on a system install that is only root/Administrators. detail (table and JSON, including "Full Command") always shows **** for secured values, even to admins, so it is safe to paste into tickets.
Generated from doc/tutorial.md. Edit it there; wiki edits are overwritten on the next sync.