Local / Testing / Remote setup query

Hi. I have setup a new test webserver so me and a colleague can work on the
same site and I have confused myself over file storage locations. In the past,
I had no problem as a solo user with local storage on my PC (eg in
c:\mydocs\sites\workingsite\ ) and test site (eg localhost - but on the same
PC) and remote (ftp site on my hosting service). Now I have to store the files
on a server (which is working fine) and also so is IIS on that server (so the
test environment is fine). And there is no problem with uploading to the real
host. And of course both he and I have copies of Dreamweaver on our respective
PCs.

When I am on the LAN, no problem. But I am sometimes outside the firewall and
so is my colleague eg we might be fixing stuff at home so the main files which
used to be "local" are now on a remote network. i.e. our work test server
hasn't moved, but our own PCs have changed location and are no longer on the
net.

What's the best way for us to setup our site definitions on our respective PCs
so we can access the work files (in a folder on the work webserver) and the
test environment (wwwroot in inetpub on the work webserver) and the real host.
And how do we setit up to allow for the fact that sometimes our PCs are on the
work network and sometimes not.

Would it be setting up a VPN so that our PCs "think" they're on the work
network so the files remain "local"? Or is the blindingly obvious staring me in
the face and I'm too dumb to notice? TIA - Gio

maybe looking into using a source control like subversion - I believe you can
use that from a website.

That way you can work from any location and make sure you dont both work on
the same files, can roll back etc.

HTH

You have the right yoyo, but the wrong string, so to speak!

You and your colleague must have separate local sites for anything to work
well. In fact, you can even have separate testing servers defined locally.
You would share files by having an intermediate 'staging server' with
Checkin/Checkout enabled.

To begin working on files, you would connect to the staging server, check
out a file, edit it, and check it back in - thus the staging server becomes
your source of files, NOT your local site, which is only your scratch area
to use for edits (and perhaps for testing).

When you are ready to publish files, you would have a second site defined -
local is the staging server and remote is the production server. This site
would be used ONLY to push files from staging to production.

Does that make sense?

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================


"Gio300zx" <webforumsuser (AT) macromedia (DOT) com> wrote

Hi. I have setup a new test webserver so me and a colleague can work on
the
same site and I have confused myself over file storage locations. In the
past,
I had no problem as a solo user with local storage on my PC (eg in
c:\mydocs\sites\workingsite\ ) and test site (eg localhost - but on the
same
PC) and remote (ftp site on my hosting service). Now I have to store the
files
on a server (which is working fine) and also so is IIS on that server (so
the
test environment is fine). And there is no problem with uploading to the
real
host. And of course both he and I have copies of Dreamweaver on our
respective
PCs.

When I am on the LAN, no problem. But I am sometimes outside the firewall
and
so is my colleague eg we might be fixing stuff at home so the main files
which
used to be "local" are now on a remote network. i.e. our work test server
hasn't moved, but our own PCs have changed location and are no longer on
the
net.

What's the best way for us to setup our site definitions on our respective
PCs
so we can access the work files (in a folder on the work webserver) and
the
test environment (wwwroot in inetpub on the work webserver) and the real
host.
And how do we setit up to allow for the fact that sometimes our PCs are on
the
work network and sometimes not.

Would it be setting up a VPN so that our PCs "think" they're on the work
network so the files remain "local"? Or is the blindingly obvious staring
me in
the face and I'm too dumb to notice? TIA - Gio