Labkey app #2
Merged
Labkey app #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The Dockerfile follows the instructions for setting up LabKey. It loads files from the tarball into the appropriate directories.
Removes db directory since we are using the base image for Postgres
Removes web directory since we are placing the labkey server into the tomcat container. Much easier to run.
|
Thanks Mario! I'll read for understanding and merge prior to our meet-up tomorrow. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updates the documentation in the README and adds a locally working docker-compose with Dockerfile. Still needs to be tested out in the SPIN world.
There was an issue setting it up between the NFS docker volume mounting and the postgres database. Also issue with getting labkey.xml to find the postgres database. The volume mounting issue was due to the fact that docker volumes are persistent and I couldn't create the postgres superuser. Solution was here: docker-library/postgres#41 (comment) (simply delete the volume mount).
I used the links keyword to give the container an alias so that we can provide that as an URL in labkey.xml (probably not necessary but it worked).
The tarball for Labkey was too big to upload so make sure to have that present and extracted if you want to try this out first. I separated out some of the directories (look at the README) and if you look at the Dockerfile, you can see how they are being copied over.