Platforms

Envlet on Fly.io

fly secrets set ENVLET_TOKEN once, then start the machine through the CLI or inject with the SDK.

Set the token
fly secrets set ENVLET_TOKEN=envlet_...
Start through the CLI
[processes]
app = "npx -y @envlet/cli run -- node server.js"

Set up

  1. 01

    Create a token

    Create an identity for Fly.io and a token for the environment it deploys.

  2. 02

    Set one secret

    fly secrets set stores ENVLET_TOKEN on the app. One app per environment keeps tokens separate.

  3. 03

    Start through Envlet

    Prefix the process command with envlet run, or call inject() at boot if you prefer the SDK.

Questions

Will my app start if Envlet is down?
No, and that is the point. It retries for a few seconds, then fails so you notice, instead of starting with half an environment.
Do I still need Fly.io's own secret store?
Only for ENVLET_TOKEN. Everything else lives in Envlet, so you rotate in one place.

Stop pasting .env files.

One command. The right values for whoever runs it.