Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Clarify how to override VIVO configuration #8

Open
awoods opened this issue Oct 23, 2019 · 0 comments · May be fixed by #9
Open

Clarify how to override VIVO configuration #8

awoods opened this issue Oct 23, 2019 · 0 comments · May be fixed by #9

Comments

@awoods
Copy link
Member

awoods commented Oct 23, 2019

There are currently two mechanisms for overriding VIVO configuration:

  1. Copying dockercompose.runtime.properties and example.applicationSetup.n3 into the configuration directory (noting that line:35 represents a bug, in that the application configuration directory is actually /usr/local/vivo/home/config and not /usr/local/VIVO/home/config)

..and

  1. Mounting the example-config directory as a volume into /usr/local/vivo/home/config

No matter what is written into the files in mechanism (1.) above, it is overwritten by the mounted files in mechanism (2.)

This issue is to resolve the confusion by removing mechanism (1.).
awoods pushed a commit to awoods/vivo-docker2 that referenced this issue Oct 23, 2019
Remove VIVO configuration mechanism that never takes effect
6e9233c 
..because it is overwritten by files in `example-config`

Resolves: vivo-community#8
@awoods awoods linked a pull request Oct 23, 2019 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove VIVO configuration mechanism that never takes effect awoods/vivo-docker2
1 participant
@awoods