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
Pretty self-explanatory. #22, #52 and #64 are related. If you're using staticfiles with the STATICFILES_DIRS setting, but are not using STATIC_ROOT, an error is raised when trying to make absolute paths for the static files. In our case, we use staticfiles in development and use a separate storage class for S3 storage of our static files. This means STATIC_ROOT is never set for us, neither in development nor in production. But, because of the has_scheme check in make_absolute_paths this luckily shouldn't be a problem in production, only in development.
The text was updated successfully, but these errors were encountered:
I ran into a similar issue while making our local dev environments work (running in debug mode with runserver). I came up with a workaround that works that I have noted in #165: #165 (comment)
Pretty self-explanatory. #22, #52 and #64 are related. If you're using staticfiles with the
STATICFILES_DIRS
setting, but are not usingSTATIC_ROOT
, an error is raised when trying to make absolute paths for the static files. In our case, we use staticfiles in development and use a separate storage class for S3 storage of our static files. This meansSTATIC_ROOT
is never set for us, neither in development nor in production. But, because of thehas_scheme
check inmake_absolute_paths
this luckily shouldn't be a problem in production, only in development.The text was updated successfully, but these errors were encountered: