Update dockerfile to speed up builds#741
Conversation
There was a problem hiding this comment.
Looks good.
(As a separate task) Would it be inappropriate to run python manage.py collectstatic via the Dockerfile? I think this might save devs1 and CI that step in client apps.
Answer
[It] makes sense for collectstatic to happen downstream. Static files need to live in a volume that's shared with the Nginx container. IDK if that setup works if they're baked into the container. Also anything that uses core-cms as a base image will need to run collectstatic again anyway. e.g. tup needs to do it to pick up tup-ui.
Also, I should test this PR thoroughly.
- Core-CMS local
- Core-CMS remote
Core-CMS-Resources localCore-CMS-Resources remoteCore-CMS-Custom localCore-CMS-Custom remote- tup-ui local (I have a clone)
tup-ui remote
Footnotes
-
The
collectstaticmight be unnecessary for devs, if they haveDEBUGset toTrue, becauseurls.py#L82-L83(since 1c326b9).2 ↩ -
2023-01-16: v4.4.1 README suggests devs might still need to run
collectstatic. ↩
There was a problem hiding this comment.
I think I understand this well now. Based on my understanding, I tested enough.
Clean up neglected by #741.
* docs: update docs since TACC/Core-CMS#741 * docs: restore debug-project.md
Overview
Update the Dockerfile to remove Node deprecation warnings in CI and streamline Python dependency installation
Related
Changes