Share the variables your app needs
One link lists the keys your app reads, with where to get each one. People fill in their own values and run.
Sep 28, 2026 · 3 min read
1. Make a template
In the dashboard, open Templates, then New template. Paste your .env.example. Your browser keeps the names and drops any values.
Well-known names like OPENAI_API_KEY or STRIPE_SECRET_KEY get a description and a link to the provider's key page. Add your own for the rest, mark some optional, and set the start command.
Templates hold variable names only. Never values.
2. Put the link in your README
The template page has Copy README badge:
markdown[](https://getmyenv.com/t/<id>)
The page is unlisted and not indexed. It can also download a .env.example with the names and comments.
3. What people do with it
- In the browser: Use this template creates a project with those names and opens Fill values, one key at a time, with a link to get each.
- In a terminal, with or without an account:
cd your-clone
npx getmyenv start --template <id>The CLI adds the names, asks for each value with hidden input, and encrypts on the machine before upload. Then it prints the run line:
npx getmyenv run -- npm run dev