I've tried to use the command
passenger-config restart-app and to add/edit the file
restart.txt in the
tmp folder from article
Restarting applications - Apache - Passenger Library and both methods are working correctly
. But the restart button still doesn´t work... I will open an issue, thanks
@Anthony!
Anyway I will use the restart.txt method
, it feats perfectly my needs
@blademsr
In a previous post, you stated
As a suggestion, I have an automatic pipeline that compile the app and upload it using ftp, but I need to manualy restart the application to apply changes.
It would be great to have some automatic restart when the application startup file is updated for example.
and I think that you should use a different perspective here, being that you first compile the application, then stop the application and upload the (newly) compiled application, followed by a start of the (new) application.
In essence, you are not restarting an application, you are starting a newly compiled application .......
In theory, uploading the (newly) compiled application should not require any Passenger restart, but it does : Passenger uses "blocking restarts" by default.
Any blocking restart is equivalent to a shutdown of processes, followed by newly spawned processes.
Now, if you are restarting the (old) application, Passenger will naturally (re-)spawn processes for the (old) application ...... with some potential delay.
If you do not encounter issues, then the (potential) delay has been large enough to upload your (new) application in time ..... even though this sounds good, it is not : it is an indication that you have very busy "server", causing delays in process spawning.
If you do encounter issues, then the (potential) delay is virtually absent ....... and the delay is not sufficient enough to upload your (new) application in time : Passenger can or will get confused and spawn some kind of problematic process.
In short, to prevent any issues of any kind, just use a "workaround" (as mentioned by
@Anthony) and to make sure that all issues are prevented, just stop the (old) application before uploading the (new) application.
By the way, Passenger Enterprise does allow for rolling restarts, but that can cause even more strange behavior.
Kind regards.....