We are currently working on implementing our Symfony 1.4 system. The system is too large to be converted to Symfony 2 and switched to night - re-dev will probably take us a year. What we are going to do is install the new Symfony 2 project, which is empty, except for one task - end-to-end!
The idea is that your browser requests example.com/products ... installing Symfony 2 recognizes that it should really request the old system, and it frizz or something like that, and goes to the old Symfony 1.4 server the same question let's say old.example.com/products ... regardless of what the server’s response from (headers, cookies, etc.) is processed by the Symfony 2 server and transferred back to the browser. The browser, however, is no wiser that it is really talking to a proxy.
Then we re-develop the module called “products” in Symfony 2, and when we deploy, we simply switch proxy “off” for this module. Thus, we adhere to iterative development, and we make the influence and training of the curve much better in the development team (and out of the business course).
I was considering mod_proxy in apache, I was thinking about installing another proxy server, but the above solution will be best for us.
The problem is that I know that Fabio did this, I think it is vimeo.com (or some other video site), but I can not find any documentation or tutorials on how this was achieved, and where should I focus on my research.
source share