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.

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

Documentation for application.properties overrides via ENV variables #275

Open
hweej opened this issue Mar 25, 2024 · 0 comments
Open

Documentation for application.properties overrides via ENV variables #275

hweej opened this issue Mar 25, 2024 · 0 comments

Comments

@hweej
Copy link
Contributor

hweej commented Mar 25, 2024

User to override application.properties via environment variables. ENV variables are currently supported in a limited or full-supported way, however it may not be clear to the end user.

Use case:

It would be helpful for users to be able to

  1. Point to specific VEP version of genome-nexus. e.g. <vep_version>.genomenexus.org
  2. Modify the enrichment fields via environment variable

Alternative (instead of ENV variables)

  1. User supplied application.properties file. Not friendly for usage in NextFlow

Deliverables:

  1. Provide examples of ENV usage, especially with docker usage.
  2. Provide example of user supplying custom application.properties file and location to file.
  3. Document the ENV variables currently being used
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant