Replace django get_random_secret_key with secrets.token_hex #478
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.
With prior dependency changes, we no longer install
psycopg
onto users' computers, but theget_random_secret_key
function used insetup.sh
requires Django to be fully set up prior to calling the function. As such, the function errors due to the missing dependency.Since the secret key generated here is only going to be used for development, we can simply replace it with a more straightforward
secrets.token_hex(32)
, despite its much lesser security.