Envlet
Start free
Platforms

Envlet on GitHub Actions

One repository secret replaces every other secret in the workflow. Steps run through envlet run and read values the normal way.

Start freeRead the docs
Set the token
gh secret set ENVLET_TOKEN < ~/.config/envlet/tokens/ci-staging.token
Workflow step
- name: Test
  env:
    ENVLET_TOKEN: ${{ secrets.ENVLET_TOKEN }}
  run: npx -y @envlet/cli run -- npm test

Set up

  1. 01

    Create a token

    Create an identity for GitHub Actions and a token for the environment it deploys.

  2. 02

    Set one secret

    gh secret set reads the token from the file the MCP server or dashboard gave you, so the value never touches your shell history.

  3. 03

    Start through Envlet

    Pass the secret as ENVLET_TOKEN on the step and prefix the command with envlet run.

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 GitHub Actions's own secret store?
Only for ENVLET_TOKEN. Everything else lives in Envlet, so you rotate in one place.

Also for

Stop pasting .env files.

One command. The right values for whoever runs it.

Start free