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
The current Dockerfile is written to download the python dependencies and setup the full app when the container starts up. This means everytime the container starts up it goes the whole process of downloading the python dependencies from PyPi and setting up the app. I was trying to bring this up in an isolated environment and realized it wouldn't work. There are other side-effects like users cannot run the generate_hashed_password with a built image in a single step.
A better way to do this would be move the python setup process from entrypoint.sh into the Dockerfile and simplify the entrypoint.sh (and in turn the startup process). If the current behavior is useful for dev purposes, the project can have a separate Dockerfile.dev with a corresponding dev-entrypoint.sh.
The text was updated successfully, but these errors were encountered:
Hi, welcome! This is definitely a change we want to have, I also don't like the current process (but I'm not a big Docker user). I'll comment on the PR.
For reference, we have another issue about Docker here: #332
The current Dockerfile is written to download the python dependencies and setup the full app when the container starts up. This means everytime the container starts up it goes the whole process of downloading the python dependencies from PyPi and setting up the app. I was trying to bring this up in an isolated environment and realized it wouldn't work. There are other side-effects like users cannot run the
generate_hashed_password
with a built image in a single step.A better way to do this would be move the python setup process from entrypoint.sh into the Dockerfile and simplify the entrypoint.sh (and in turn the startup process). If the current behavior is useful for dev purposes, the project can have a separate Dockerfile.dev with a corresponding dev-entrypoint.sh.
The text was updated successfully, but these errors were encountered: