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

method to update langs.properties from app repo #14

Open
akostadinov opened this issue Jan 22, 2015 · 3 comments
Open

method to update langs.properties from app repo #14

akostadinov opened this issue Jan 22, 2015 · 3 comments
Labels

Comments

@akostadinov
Copy link

Cart should allow user to update langs.properties just like vertx.env. Otherwise a lot of flexibility is lost. For example there is no version of mysql-postgresql module version that works with the default scala language module. Users would want to update language modules according to their needs for many other reasons as well.

@nscavell
Copy link
Contributor

Is ssh'ing into the app and changing it that much of a problem ? For starters I don't think it's something that will change that often. You ssh into the machine, change it, done. I don't think cluttering the app directory with runtime configuration which may or may not be changed would be nice.

@akostadinov
Copy link
Author

if repo/configuration directory is first in the classpath, I think this can make it. If user puts in there logging, langs or cluster configuration, then it would be picked by vert.x with priority before the defaults. This would allow one to keep all app configuration in git. This is the spirit of OpenShift cartridges. If you can't easily recreate your app by your git repo, then it's already degraded UX.

I tried setting -classpath in vertx.env -> VERTX_OPTS to no avail. Seems like it needs to be done from the cartridge scripts themselves.

@nscavell
Copy link
Contributor

I think you can set CLASSPATH env variable. If we can just add configuration dir to the classpath to solve the problem, maybe that will work. PR's are welcome :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants