fix: check for arches dir and set ARCHES_ROOT #7
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.
Description
This checks to see if an arches repo lives in the parent directory.
If it does it sets ARCHES_ROOT to that directory, if not it sets it as an empty string
An additional docker-compose file has then been created which contains the additional volume mounts for ARCHES_ROOT. If the variable has been set, these are applied with the original in the volume mounts.
Test
Run a copy of arches without the base arches.
The instance should start without an ARCHES_ROOT error.
Add the arches root dir into the parent directory, add a log statement somewhere that will run
Restart the containers and see if the log statement is visible
Additional
I believe we may be able to adjust this to automatically build mounts for any apps that we want to install. If we set up an app dir in the parent directory we could build an additional docker compose to create the mount paths