-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
Add support for setting the application key in .env files when running key:generate #29
Comments
Ping @ericp-mrel, maybe you'd like to reopen the PR you've made on OC to fix this? |
Yeah, I can re-create a PR since OctoberCMS rejected my changes. |
PRs have been created. Let me know if there's anything I need to do or could improve in the PRs. |
This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days. |
This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days. |
This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days. |
Going forward (1.2+) .env files will be first class citizens in Winter so we no longer wish to support setting the application key in the config file by default. If someone has a legitimate need for it we can re-evaluate in the future but as of wintercms/storm#40 the key:generate command is reverted back to mostly the Laravel default (exception is that it will generate a .env file if none exists). |
See:
The text was updated successfully, but these errors were encountered: