fix(ci): resolve ImproperlyConfigured database error during CI-CD deploy job #226
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
lisad
approved these changes
Nov 20, 2025
aaronjae22
deleted the
ci-cd/fix-improperlyconfigured-database-conn-string
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There is a
ImproperlyConfigurederror that occurred because the "Extract deployment URL" step was importing Django settings (to readALLOWED_HOSTS) before theDJ_DATABASE_CONN_STRINGenvironment variable was available, and before database migrations had run.This PR moves URL extraction step to run after the "Run migrations" step and changes implementation to read from existing
SITE_URLsetting in DjangoCloses #225