joshuatcasey
commented
2 years ago I wonder if there's a more graceful way to restart httpd and nginx to handle the case when the configuration changes. It appears this may be possible, but I have yet to test.
httdp
Send a reload or a graceful command? https://www.cyberciti.biz/faq/apache-2-reload-httpd-config-file-unix-linux-command/
nginx
Send the hangup signal to the process? https://nginx.org/en/docs/control.html
It has been recently demonstrated that live reload will work without watchexec for nginx and httpd servers. Live reload exists in the servers by default. Therefore, this issue is to evaluate the impact of removing watchexec from webservers.
Questions
Do we actually know of anyone that is using live reload with web servers right now? Is watchexec needed to reload the nginx or httpd process in the case that the conf file changed? Or will nginx or httpd automatically pick up these config changes? Is this even a common workflow for users/developers? Is there a significant difference in performance with watchexec? If app developers are changing code frequently, is watchexec or httpd/nginx more performant?