Almost deadlock-free transition between two different web servers
When I made the transitions between apache, lightttp and then nginx, I got to a very interesting " tips and tricks ".
There is nothing clever here, but it can help someone.
The point is: a new web server is hung up on, say, port 81 and is debugged there in every way (if you have php as fastcgi it is generally very convenient).
When we finish setting up a new web server, we change the config of the old one, hanging the old server on port 81, and the new one, respectively, on the 80, with one command “swap them”.
')
We leave the old web server “just in case” for a few days, all of a sudden we have configured something wrong and it does not work as expected under load.
For example: when moving from lighttpd> nginx:
So here, with a second downtime.
PS Similarly, you can "switch" and DNS services, and mail, and much more.
There is nothing clever here, but it can help someone.
The point is: a new web server is hung up on, say, port 81 and is debugged there in every way (if you have php as fastcgi it is generally very convenient).
When we finish setting up a new web server, we change the config of the old one, hanging the old server on port 81, and the new one, respectively, on the 80, with one command “swap them”.
')
We leave the old web server “just in case” for a few days, all of a sudden we have configured something wrong and it does not work as expected under load.
For example: when moving from lighttpd> nginx:
/etc/init.d/nginx stop; /etc/init.d/lighttpd stop; /etc/init.d/nginx start;/etc/init.d/lighttpd start;So here, with a second downtime.
PS Similarly, you can "switch" and DNS services, and mail, and much more.
Source: https://habr.com/ru/post/64876/
All Articles