We Are Forking dotenvy into dotenv-ng

📝 Discussion Summary (Click to expand)

Three dominant themes

Moving away from .env – many commenters argue that .env files are outdated and should be replaced with safer, more maintainable solutions (e.g., direnv, mise, or the new dotenv-ng).

“I think .env is definitely something that should not exist.” – dolni
Protecting secrets and adopting guard‑like safeguards – the discussion repeatedly stresses treating secrets as high‑risk resources, using “missile‑launch‑switch” style checks to avoid accidental exposure.

“> the guard over the missile launch switch” – fragmede
Process over tooling – participants note that no library can replace careful human workflow; even a two‑key approval system only works if the underlying process is rigorously followed.

“But migrating away from .env starts with reading it correctly.” – hinkley

🚀 Project Ideas

A capability‑based secret guard that prevents accidental leakage of API keys, passwords, and other secrets while enforcing multi‑person approval for any operation that injects secrets into production.
Core value proposition: eliminates secret‑dump bugs and enforces process safety through dual‑approval workflows.

Key	Value
Target Audience	Security engineers, DevOps teams, Platform teams handling production changes
Core Feature	Automatic detection of secret usage, requires two explicit approvals before any secret is written or executed, integrates with CI/CD pipelines
Tech Stack	Rust backend, React front‑end, PostgreSQL, OpenAPI
Difficulty	Medium
Monetization	Revenue-ready: SaaS subscription per team (monthly $15)

HN commenters highlighted the “two key system” and “molly guard” concepts; this tool materializes those ideas into a usable workflow.
Provides practical utility by turning abstract security discussions into concrete, automated safeguards for production environments.

A lightweight approval gateway that mandates dual confirmation for any destructive command (e.g., rm -rf /, database wipes) to prevent single‑person errors.
Core value proposition: reduces production outages caused by unilateral destructive actions through built‑in recency and priming mitigations.

Key	Value
Target Audience	Site reliability engineers, Incident response leads, On‑call engineers
Core Feature	Interactive CLI that prompts two distinct users to repeat a high‑level request, validates URL and parameters, logs approvals
Tech Stack	Go microservice, SQLite, gRPC, Swagger UI
Difficulty	Low
Monetization	Revenue-ready: Tiered licensing (Free for up to 5 users, $30/mo per additional user)

Directly addresses hinkley’s concerns about “guard over the missile launch switch” and the need for a two‑person confirmation process.
Sparks discussion on process safety and offers a reusable tool that can be embedded in existing CI/CD or operational tooling.

An integrated environment manager that consolidates direnv, mise, and SecretSpec‑style secret handling into a single CLI, removing the need for multiple .env parsers.
Core value proposition: simplifies project setup across polyglot stacks while securely managing secrets and tool versions.

Key	Value
Target Audience	Developers maintaining multi‑language monorepos, Tooling engineers, Workshop participants
Core Feature	Unified config file format that can be sourced by any language, automatic secret detection, version‑aware tool installation
Tech Stack	Rust CLI, YAML parsing, SQLite for secret store, documentation via MkDocs
Difficulty	Medium
Monetization	Hobby

Responds to drdexebtjl’s observation that “dotEnv is self sustaining” and the community’s fatigue with fragmented env tooling.
Offers practical utility by unifying disparate environment‑management practices into a single, maintainable solution, likely to generate enthusiastic discussion on HN.