Can the Staging Area point to another machine?

Scenario:
Two Unix boxes are serving as development environments while an NT serves as the Staging Environment and another NT serves as the Production Environment. In a new strategy, we are implementing template-generated ASP code.

Question:
How can we configure it such that TeamSite points to a remote server in order to view such ASP files? In other words, when you click on any file in TS, Unix would not natively recognize the ASP so how can we configure it so that it, by default, points to a different environment to view te file?

Thanks,

Dave

Find more posts tagged with

Comments

Migrateduser

Hi Dave.

Look at the documentation for iwproxy in the Administrator's Guide. It includes several examples of doing something similar to this.

Considering that you want the files to actually live in TS, I think my approach would be to share out the entirety of /iwmnt via Samba. Make sure that the webserver user on NT has permissions to access the whole thing (mind the security implications there), and then use IIS on the NT machine as the customer web server. Mind you, this only works if you are using 5.x.

Specifically, your iw.cfg should have something like this (supply proper values for things in brackets):

[iwproxy]
iwproxy_host=<name or ip of TS server>
customer_webserver_host=<nae or ip of windows server>
iwproxy_port=1080
customer_webserver_port=<port that IIS is running on>

Migrateduser

Another option would be to use some carefully crafted iwproxy preconnect remap regexs to only pass asp previews off to IIS to be previewed. This sort of thing is done with Turbo to redirct jsp/servlet off to a secondary machine for processing by an application server. The same sort of regexes can be used for asp.