Add SESSION_COOKIE_SECURE to production docs #457
Merged
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.
brief description of changes
We didn't have explicit guidance around this setting before, but it was warned about by
manage.py check --deploy path.to.production.settings
, which we recently added to the upgrade instructions in 7.6.0.md for extra visibility, even though we also link to the the django deployment checklist here in this document, which advises the same action).Do we want to describe the other action items that users are likely going to need to care about after they see the output of
manage.py check --deploy
?