You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently tried to upgrade my project dependencies from 4.2 to django 5.0 as part of a major upgrade and all of a sudden in my deploy process the collectstatic job went back to its default behaviour, collecting files to /app/static. No sign of error in none of my containers.
After a while, I found out that downgrading django back to 4.2 resolved the problem, with no other modification of my code base the static files deployed to minio again.
Please let me know if you have any idea of what could cause my issues, here are some relevant parts of my project code base:
Hello there!
I recently tried to upgrade my project dependencies from 4.2 to django 5.0 as part of a major upgrade and all of a sudden in my deploy process the
collectstatic
job went back to its default behaviour, collecting files to/app/static
. No sign of error in none of my containers.After a while, I found out that downgrading django back to 4.2 resolved the problem, with no other modification of my code base the static files deployed to minio again.
Please let me know if you have any idea of what could cause my issues, here are some relevant parts of my project code base:
requirements.txt
settings.py
(Static files config part)The text was updated successfully, but these errors were encountered: