-----Original Message-----
What are the best practices for allowing multiple users
to update a website? ie/ shared staging network drive
configuration, publishing, permissions, etc. Has anyone
set this type of usage before? Thanks in advance.
First, if possible, segregate the site into subwebs. This
will minimize the number of people working on any one
subweb.
Then, plan on a three or four tier architecture. The
three tiers look like this:
At the top, your production server(s).
In the middle, an integration server.
At the bottom, personal Web servers or disk-based
for each developer.
Individual developers publish to the integration server
for testing, and then an admin publishes from the
integration server to production.
Four tiers look like this:
At the top, your production server(s).
* Below that, an staging image of your production
server.
In the middle, an integration server.
At the bottom, personal Web servers or disk-based
for each developer.
The idea here is that individual developers promote their
work to the integration server. Then, an admin promotes
new or changed content to the staging image for final
testing. If that works, the change goes to the
procdcution server. If it doesn't, you can always back
out but copying production back to the staging image.
Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------
