Add support for setting the application key in .env files when running key:generate about winter HOT 7 CLOSED

Yeah, I can re-create a PR since OctoberCMS rejected my changes.

from winter.

PRs have been created. Let me know if there's anything I need to do or could improve in the PRs.

from winter.

Ping @ericp-mrel, maybe you'd like to reopen the PR you've made on OC to fix this?

from winter.

This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

from winter.

This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

from winter.

This issue will be closed and archived in 3 days, as there has been no activity in the last 60 days.
If this issue is still relevant or you would like to see it actioned, please respond and we will re-open this issue.
If this issue is critical to your business, consider joining the Premium Support Program where a Service Level Agreement is offered.

from winter.

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).

from winter.