Humdinger Multi-Server Problem
-
Here’s my scenario. Someone tell me if I should stop trying to make it work and just do something else.
We’re trying to install WP in a higher education environment that runs a MS shop. Take note of the following “players”
2 v-lans (one “private”/192.168… and one “public”/10.10…)
2 MS Windows Server 2003 boxes (server 1 on the private and server 2 on the public vlan).server1 is the school’s webserver using IIS (a separate issue i’m not worried about right now), PHP and containing mulitiple directories: https://www.server1/etc
server2 has been setup with MySQL
My director would like for the wordpress site to be located at https://www.server1/wordpress (IIS+PHP) with the database on server2. (Simple enough).
The problem is that the wordpress site will contain gigs of resources (mp3’s, video’s, etc) and my director doesn’t want to give up the HDD space on server1. He also doesn’t want to give up a dedicated ip address to sever2. argh!
I figure I have 3 options (you need to tell me if 1 and 2 are actually possible, and if so, how.) If options 1 and 2 are not possible, I can stop scratching my head and tell my director he has to either drop the project or go with option 3.
The Options
1) Install wordpress on server2 with the database and place the index file on server1.com/wordpress (remember they’re on different vlans and server2 can’t have a dedicated ip from the outside). Is there a way to create a tunnel?2) Install wordpress on server1.com/wordpress and redirect the upload folder to server2. (Could I used a mapped drive on server1?
3) Resort to a dedicated ip address for sever2. (note, I realize this is the easiest, but it is not desired by my director. Therefore, try to restrain from just replying “option 3” without some input into why that’s the only option.
This is long. I’m sorry. I’ve been racking my brains all day though. If you have a couple minutes to think about it, i’d appreciate it.
- The topic ‘Humdinger Multi-Server Problem’ is closed to new replies.