Posted by tema on October 4, 2012 at 5:43am
Is it possible that a number of particular paths requested from one site would be rendered by another site based on another Drupal core version without redirecting to another domain?
For example:
- http://example.com/some/path - Drupal 6.x, standard situation;
- http://example.com/some/another/path - Drupal 7.x, another site.
It could be helpful for big projects to upgrade it step by step. My situation is even more complicated by the fact that I had to use another Octopus instance for 7.x site because my application requires PHP 5.3+.
I'm new to Nginx, so maybe this question will seem ridiculous to you. Sure, I can use third domains for upgraded parts, just trying to find more elegant soultion.
Comments
Yep
There are at least three ways to do it:
Using specific locations with different roots.
Using
mapto direct to the appropriate drupal backend.Setting up a reverse proxy in front.
The third solution is not the easiest, but is the one that will allow you to do the migration more easily. When it's done you just remove the reverse proxy et voilà.
All migration details are located in the reverse proxy config.