| 6:57 pm on Jan 8, 2010 (gmt 0)|
It is much easier if you use a subdomain rather than a subdirectory - see this thread:
| 11:09 pm on Jan 11, 2010 (gmt 0)|
Yah, that's what we have it now, but I'd like to move it to sub dir for SEO reason (mainly so that when people link to our blog, they'll link to our root domain).
| 9:56 am on Jan 12, 2010 (gmt 0)|
You could set up a reverse proxy.
It could either be one of the servers you will have anyway, or a separate one.
I have not done this myself, but it looks to me that Apache with mod_proxy or a number of other web servers (e.g. nginx, Lighttpd) could both run Wordpress and forward requests not for the Wordpress directory to your windows server.
If you want easy set up you might try Cherokee: there are step by step instructions for setting up Wordpress and a nice web admin interface.
| 11:30 pm on Jan 13, 2010 (gmt 0)|
Cherokee looks interesting, I think I'm going to give that a try.
Is that kind of like xamp?
| 11:39 pm on Jan 13, 2010 (gmt 0)|
BTW, with Cherokee, will I able to run my windows app on the main domain and use cherokee to run wordpress on a sub directory?
| 11:48 pm on Jan 13, 2010 (gmt 0)|
by windows app, I mean IIS 7
| 4:59 am on Jan 14, 2010 (gmt 0)|
|Is that kind of like xamp? |
No. Its just a web server. You will need to install php-fcgi and mysql separately (usually pretty trivial on Linux) and configure cherokee to use php (the docs on the cherokee site are clear).
I think so. I use Cherookee only as an easy to reconfigure development server (although that might change soon).
|BTW, with Cherokee, will I able to run my windows app on the main domain and use cherokee to run wordpress on a sub directory? |
As far as I can see from the docs, you can. You should be able to add a regular expression rule with an http reverse proxy handler that will forward anything not for the Wordpress subdirectory to the server running IIS.
It should be fairly straightforward, but please let me know how it works.