Some sorts of obvious and quickly-caught errors that slip past you on the way to deploy, don't throw an exception as soon as you run the start command, but still throw within a (short) predictable period after boot. (For instance, some misconfiguration that's preventing your app from connecting to the database, for completely obvious reasons; but still not throwing until five seconds into boot-up.)
I'd love to see a flag, or simply a longer default, to modify the delay that the local jitsu deploy command waits. That way, we don't get “Nodejitsu ok” when, in fact, it immediately crashed; this also saves me having to open the website to check the log and see what actually went wrong.
Some sorts of obvious and quickly-caught errors that slip past you on the way to deploy, don't throw an exception as soon as you run the start command, but still throw within a (short) predictable period after boot. (For instance, some misconfiguration that's preventing your app from connecting to the database, for completely obvious reasons; but still not throwing until five seconds into boot-up.)
I'd love to see a flag, or simply a longer default, to modify the delay that the local
jitsu deploycommand waits. That way, we don't get “Nodejitsu ok” when, in fact, it immediately crashed; this also saves me having to open the website to check the log and see what actually went wrong.