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

FR: Ability to change default environment setting #2355

Closed
thestepafter opened this issue Feb 20, 2019 · 4 comments

Comments

Projects
None yet
3 participants
@thestepafter
Copy link

commented Feb 20, 2019

Is your feature request related to a problem? Please describe.
Ideally we would be able to change the default environment from production to something else. For example, I have 10 people on my team and until we create a .env everyone is working in production. Because of this production has become our default development environment even though it is called production. This means that we have had to use live as our production environment name.

Describe the solution you'd like
The ability to change the default environment in the control panel.

Describe alternatives you've considered
We use live for our production environment and production as our development environment name.

Would you be willing to sponsor this feature?
It depends on the cost.

@thestepafter thestepafter changed the title Change default environment FR: Change default environment Feb 20, 2019

@jackmcdade

This comment has been minimized.

Copy link
Member

commented Feb 20, 2019

This is not best practice. Every developer should set their .env file as part of the onboarding process for the project. production is the standard default (e.g. unset) environment, and I don't want to change this behavior, it would throw thousands of people (and sites) off.

@jackmcdade jackmcdade closed this Feb 20, 2019

@thestepafter

This comment has been minimized.

Copy link
Author

commented Feb 21, 2019

@jackmcdade

I'm not asking you to change the standard behavior, just asking for a way to control the behavior in the control panel or even just a YAML file.

You can still default to production, just give a way to override it. Just because it's standard behavior doesn't mean everyone is going to follow it. This is a way to prevent issues occurring because if someone doesn't setup the .env and makes a change Spock is going to fire and a bunch of other negative things could happen

Assuming production by default is just asking for problems when someone downloads a project and starts working in it.

@thestepafter thestepafter changed the title FR: Change default environment FR: Ability to change default environment Feb 21, 2019

@thestepafter thestepafter changed the title FR: Ability to change default environment FR: Ability to change default environment setting Feb 21, 2019

@jackmcdade jackmcdade reopened this Feb 21, 2019

@jackmcdade

This comment has been minimized.

Copy link
Member

commented Feb 21, 2019

Fair enough! I get it now. Here's all you'll need to do to change the default environment in the next Statamic update:

image

@thestepafter

This comment has been minimized.

Copy link
Author

commented Feb 21, 2019

This is wonderful, thank you!

@jasonvarga jasonvarga closed this Mar 27, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.