Refactor docker-compose to support running jobs. #16
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows running girder_worker jobs at the expense of a more complicated deployment.
The previous docker-compose used docker volumes for the database and assetstore. Because of docker permission weirdness, docker volumes don't work once the container is run with a specific user, but running with a specific user is needed for a docker to start another docker container, so the assetstore and database are now stored in subdirectories in the devops/annotation_tracker directory. Migrating a previous deployment would involve copying these files from the docker volume to these subdirectories and ensuring that all files are owned by the current user.