Closed ksilin closed 7 years ago
start command could not include env variables, use env. something like this:
env "JAVA_OPTS" => "-Xmx8G #{ENV["JAVA_OPTS"]}"
start_command "main/target/universal/stage/bin/export-main -- -x 4"
demonize true
https://github.com/kostya/eye/wiki/About-start_command https://github.com/kostya/eye/wiki/Using-ENV-variables-in-config
Wonderful! Many thanks, now I have got it working perfectly.
Just one more thing I am wondering about. If the demonize
flag is not set to true
, the application status remains at starting
, although it is running and the app will be restarted again and again after a while. Is there an explanation of the behavior I might have missed somewhere?
when daemonize false, your app should create pid file which eye trying to find, if it not created eye couldnot monitor it. in daemonize true, eye daemonize process and create pid_file for it.
got it, thanks again!
start_command "JAVA_OPTS=\"-Xmx8G $JAVA_OPTS\" main/target/universal/stage/bin/export-main -- -x 4"
expected behavior: command runs with specified JAVA_OPTS & providede params
the same start command works as expected with god
current behavior:
however, the process does not run:
the log explains the reason
Can I prevent eye from splitting the command before running it and/or not assuming the assuming the first whitesppace-delimited chunk is the command to run?