Skip to content
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.

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

Added nicer usages of environments #12

Closed
wants to merge 1 commit into from
Closed

Added nicer usages of environments #12

wants to merge 1 commit into from

Conversation

dennie170
Copy link

With this new feature, it becomes super simple to use multiple environments.

First we create an .local.env or a .production.env, and secondly we create a .env file that only contains local or production.

@rappasoft
Copy link
Owner

I'm confused. Wasn't this how 4.2 did it? Why do you need testing and production? There should just be one .env file that's gitignored, so which ever is in its place will be used. Isn't that the flow of things with L5?

@dennie170
Copy link
Author

Yes, this is basically how 4.2 works. I just don't like the concept of a singular .env file.
You can close the request..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants