Templates

A template is a list of variable names, with an optional description and link for each, plus an optional start command. It has no value field, so it cannot hold a secret.

Anyone with the link can view it. Put one in your README so people who clone your app know which keys to get.

• Open Templates in the dashboard, then New template.
• Paste a .env or .env.example. Your browser keeps the names and drops the values before anything is sent.
• Or start from a project: context settings, Share as template. Names only.
• Well-known names get a description and a link to where you get the key. Edit or clear them.

Up to 20 templates per account, 200 names each.

On the template page, Use this template creates a project with those names and opens Fill values. Values are encrypted in your browser.

Or in the app folder:

bash
npx getmyenv start --template <id or link>

The CLI links the folder (guest or sign in), adds the names, then asks for each value with hidden input. Enter skips one. In a folder that is already linked, it adds the names to that project.

You can also download a .env.example with the names and comments.

For well-known keys we check the shape of a value where you type it, in the browser or CLI, and show a hint if it looks off. The value is never sent for the check. A hint never blocks saving.