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

Is the default config overrideable without updating the jar? #53

Closed
buggtb opened this issue Dec 22, 2016 · 2 comments
Closed

Is the default config overrideable without updating the jar? #53

buggtb opened this issue Dec 22, 2016 · 2 comments

Comments

@buggtb
Copy link
Collaborator

buggtb commented Dec 22, 2016

I don't know if I'm just missing something or its not done yet, can I define an external site-default.yaml type config file?

@thammegowda
Copy link
Member

Yes!
You can prefix your file to the classpath to override it without updating the jar.

I use bin/sparkler.sh script; it prefixes the resources in ./resources/ directory to classpath.
java -cp $DIR/resources:$JAR edu.usc.irds.sparkler.Main $@

Currently, we place such files in conf directory, all changes made here are tracked in git.
Maven will make a copy of it to resources directory. Here you can modify it at runtime. if you dont need these changes to be pushed to repo you can safely ignore it (otherwise, please copy the changes to conf to checkin!)

Please close this issue if it solved, or if you have suggestions I would like to listen :-)

@buggtb
Copy link
Collaborator Author

buggtb commented Dec 26, 2016

Cool. Personally I think it would be much more convenient to have a --config-dir type flag on the command line or something but this will do for me! (maybe add it to a wiki page somewhere)

@buggtb buggtb closed this as completed Dec 26, 2016
buggtb added a commit that referenced this issue Oct 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants