Let nginx reverse-proxy deliver data from source system until transfer is finished
It would help us, if during a migration, while the destination system got the domain configuration, but not yet the data, the nginx-component of the destination server would work as reverse proxy for the source system.
So a client, requesting data for a domain from the destination server could already be served content, even though the data is not yet transferred. After the transfer is completed, the configuration can be changed back to the usual “nginx points to local apache” configuration.
Martin
shared this idea
Thank you for your input!
Unfortunately, we have to close your request, because over the years it has not become quite popular for further implementation.
—
IG
-
Martin
commented
Actually our current workflow during migrations is the other way round: To avoid having to change DNS or switch IP, we take the source system down first and assign it a new IP, while we set up the target with the IPs, which previously belonged to the source server. Then we start the migration.
This results in a downtime during the migration, which we inform our customers of. The websites come back one after another, when the respective data are transferred.
But it would be much cooler, if the nginx-reverse-proxy could pass on the requests to the source system to minimize the downtime.