ddae8d91f6
When the container is mounted, the local contents of . obscure /app/symposion_app in the image. Generally speaking, this is handy for development, as it means that local changes are detected and used immediately without needing to restart the container. However, it breaks in the specific case of the sass->css generation. Prior to this change, the css is generated only after the first time a page is hit. The generated file is placed in static/build; however, due to the obscuration, this generated file isn't visible to the running process. The next time the container is built, the pre-existing static/build directory is copied into the container as it's being built; then, later, that version is what gets served. This change adds the needed libraries to pre-generate the css as part of the image build, and runs compilescss to do this, prior to the collectstatic step. It also adds a second collectstatic into the make_dev_container script, so that the visible static/build directory should ahve the same contents as the obscured static/build directory. It also expands the .dockerignore file to make sure these files aren't copied into the image in future. I'm not sure if this is the right thing to do, as changes to this directory will be ignored, which could be confusing. Perhaps never being able to see these generated files is better?
8 lines
77 B
Text
8 lines
77 B
Text
.git
|
|
symposion-tools
|
|
docker
|
|
static/build
|
|
*.sh
|
|
TODO
|
|
dev-env.sh
|
|
.gitlab-ci.yml
|