The same configuration on every machine and in CI.
Keep development variables per app and environment, and pull them with one CLI command — on a laptop or in your pipeline. No more .env files passed around in chat.
From dashboard to .env in one command.
Every developer and every pipeline gets exactly the values assigned to them.
- 01
Add your variables
Create development variables for each app and environment in the dashboard.
- 02
Sign in to the CLI
Install it from npm, point it at your Smart Grow server and sign in on your device.
- 03
Pull them anywhere
download_variables writes your .env. In CI, use an API token instead of a personal session.
One CLI, locally and in CI.
Framework-agnostic: the CLI writes a standard .env (or env) file that any stack can read.
npm i -g @smart-dev-agency/smart-grow-secure-cli
smart-grow update_config_cli # set your Smart Grow server URL
smart-grow login # sign in on this device
smart-grow download_variables # pick app and environment, writes .env# The runner's CLI must point at your server (smart-grow update_config_cli).
- name: Pull development variables
run: smart-grow download_variables_with_token --output .env
env:
SMARTGROW_ONPREMISE_API_TOKEN: ${{ secrets.SMARTGROW_API_TOKEN }}
SMARTGROW_ONPREMISE_APP_ID: ${{ vars.SMARTGROW_APP_ID }}
SMARTGROW_ONPREMISE_ENV_ID: ${{ vars.SMARTGROW_ENV_ID }}What you get.
Every item here is something the product does today.
-
Per app and environment
Development, QA and production each keep their own values.
-
Framework-agnostic
Output as dotenv or env format, to the file you choose.
-
API tokens for CI
Create tokens per app and environment, with an expiry date, for your pipelines.
-
Encrypted at rest
Values are stored encrypted and delivered over a post-quantum channel on top of HTTPS.
-
Roles and audit log
Limit who can read or change each environment, and see every change.
-
Revocable CLI sessions
See which devices are signed in to the CLI and revoke them at any time.