adding a wordpress site to IIS production website

[bookouri]

I have a production web site located in the default

http://wwwroot

folder. ITs the only web site running on this server.

we have been developing a wordpress site and it is located in

http://wwwroot\dev.

Now Im ready to make the wordpress site the default that internet users see when they go to

http://www.myurl.com.

But, I dont want to just dump the wordpress site into

http://wwwroot

because I have some .asp pages that allow internal users to log on to non-public pages and i just dont want to mix all that stuff up. I want my users to still be able to go to

http://www.myurl.com\asp\logon.asp.

I planned to create a /prod folder and copy the /dev site into it and keep a dev and a prod site available.

Ill end up with somethign like this:

http://wwwroot

/dev
/prod
/asp

I think I can then have the sites IP address/url redirected to

http://www.myurl.com/prod

so that normal visitors will get the production wordpress site like they should when they go to

http://www.myurl.com.

Then developers can go to

http://www.myurl.com/dev

to test new stuff. My secured users should then be able to still go to

http://www.myurl.com/asp/logon.asp.

But Im not sure if this will work. What is the best way to accomplish this. I dont have any experience running multiple web sites on one server.

Can anybody tell me if Im way off track?

thanks

 

[Dinkytoy]

Generally if you are setting up multiple sites you should set them up invidividually within IIS. I.e. one for Dev, one for Prod etc.

What you could probably do if you want to set it up this way is have a default asp file in

http://www.myurl.com/

to redirect all traffic to

http://www.myurl.com/prod

then have your dev and secured users access the url

http://www.myurl.com/dev

or

http://www.myurl.com/dev

directly.

I don't like this solution though since anyone can get to your dev area and it quickly gets messy, especially as an error in dev could take down your entire site.

What I would do is create 3 sites.

http://www.myurl.com

asp.myurl.com
dev.myurl.com

They can all live on the same IP address, but make sure you assign a host header value to at least 2 of them and secure them further with permissions if you can.

 

[bookouri]

i think you're right. i think im going to go ahead and create the 3 sites.

thanks for the reply