Add data migrations for Django Site and OAuth2 Application
#318
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
The `Site` migration is from the upstream Resonant cookiecutter. The `Application` migration will improve automation. It should be fine to pick a distinct client ID and hardcode it into the frontend; multiple deployments can use the same client ID, since none will have multiple instances of the same frontend connected to a single backend.
naglepuff
approved these changes
Jan 30, 2026
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
Sitemigration is from the upstream Resonant cookiecutter.The
Applicationmigration will improve automation. It should be fine to pick a distinct client ID and hardcode it into the frontend; multiple deployments can use the same client ID, since none will have multiple instances of the same frontend connected to a single backend.