New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

.env file defaults & strategy #16

Open

joshuapease opened this issue May 22, 2024 · 0 comments

Contributor

joshuapease commented May 22, 2024 •

edited

Loading

Provide a happy path for maintaining .env vars for a project.

Should we keep DDEV from mucking these up?
Should we hard code DB connection details in the DDEV config? Having those as .env vars don't really do much.
Is there much benefit to the dev, production, staging versions of .env.example?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment