You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
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 :)
Cart should allow user to update
langs.properties
just likevertx.env
. Otherwise a lot of flexibility is lost. For example there is no version ofmysql-postgresql
module version that works with the defaultscala
language module. Users would want to update language modules according to their needs for many other reasons as well.The text was updated successfully, but these errors were encountered: