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
Solve tracker has a setting that points to the git repo where solves are to be committed. This directory would need to be included in the docker image (and should probably be a volume so that changes are seen outside of the container)
The text was updated successfully, but these errors were encountered:
Mounting as a volume works. Technically we could add a clone command to the Dockerfile, the risk there is that we make commits, don't push, and then when the image goes down we lose the commit.
If we keep using a volume, we may want to use docker-compose to start up the container with the volume mounted. Let me think of this when I get back home.
Solve tracker has a setting that points to the git repo where solves are to be committed. This directory would need to be included in the docker image (and should probably be a volume so that changes are seen outside of the container)
The text was updated successfully, but these errors were encountered: