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
Spurred on by #1989 and #1995 (potentially also spurned), we discussed how best to overwrite static content for custom deployments. Mainly impacts the background/favicon
We should rely on collectstatic and add in an appropriate STATICFILES_DIRS.
As discussed on MIT-LCP#1996,
we are making the theme customizable for deployment
by .env configuration. This lead us modifying existing css files
adding configurable image files.
This folder should be used to store deployment specific
static files.
It is expected that compilestatic will be ran first(which will
generate the css, image files and store them to the static-override folder),
and then collectstatic will be ran which will collect static files
from static and static-override directories
Note that, the `static-overrides` comes before the `static` on base.py
This is intentional to make sure `static-overrides` is given
first priority if there are same file in these two directories.
Spurred on by #1989 and #1995 (potentially also spurned), we discussed how best to overwrite static content for custom deployments. Mainly impacts the background/favicon
We should rely on collectstatic and add in an appropriate STATICFILES_DIRS.
Currently it's set here in the base settings:
physionet-build/physionet-django/physionet/settings/base.py
Line 177 in 3e18d61
Seems like we could change this to something like:
Then we'd just have a .gitignore in static-overrides and let repos store non version controlled content there
The text was updated successfully, but these errors were encountered: