Generate APP_SECRET in .env.local when missing #1531
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
| This proposal is smart, but I think it's convoluted for the Demo application. Also, it introduces a new "moving part" that could fail. Is it really wrong to ship this Demo application with a predefined value in |
| Closing in favor of #1532 |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
The demo app needs an APP_SECRET because it uses ESI, fragments and remember-me, which all need a secret.
Instead of hardcoding a secret in
.env, I propose here to generate one in.env.localoncomposer i/uwhen it's missing.Inspired by the discussion on #1529 (comment)