Browse topics

Teams & onboarding

Not shipped yet: Automated CI checks, policy enforcement, and "sync to pipelines" are roadmap ideas, not in the CLI today. This page is about how teams think about the template today and what is planned. For what actually runs on a machine, use Commands. For timelines, see the Roadmap.

How teams use genesis-env with a single committed template and a repeatable local setup. This matches what the CLI supports today: init, generate (default genv), and validate.

Shared template in the repo

Keep one committed template in the project root (see format and line rules in Templates & .env). Each developer generates their own .env locally. Never commit secrets.

Contributor workflow

After cloning, follow the Sample workflow on the Commands page (genv init once if needed → edit the template → genv → genv validate). Document new keys in your README when you change the template. Use genv --force only when you intend to replace an existing local .env.

CI / automation

The current CLI is focused on interactive setup on a developer machine. genv validate is for local checks before you commit or deploy; it is not a substitute for your own pipeline policies.

If you need a lightweight CI check without inventing CLI features, you can assert that the template exists, for example:

yaml
# Example: fail the job if the template is missing (shell only)
- name: Require env template
  run: test -f .env.template || test -f .env.example

For future direction (validation in CI, policy, and so on), see the Roadmap and your repository's docs/ROADMAP.md if published there.

Planned ideas (not in the CLI yet)

The following are not shipped features. They are only roadmap style ideas:

  • Role based access to who can change templates
  • Audit logs for template changes
  • Organization wide policy enforcement
  • Multi environment variable management with inheritance

Support & feedback

Questions, ideas, or contribution guidance: use this page and your project's usual channels. For the open source CLI repo, see GitHub. For enterprise support, contact your organization's maintainers of genesis-env.