From: Sven Liessem <sven_liessem@ho...> - 2000-05-16 01:42:39
Coming back to a discussion we had some time ago.
I need to have more than one developer to work on a
site. The idea here was to put the site under CVS
control and let everybody work on it's own copy.
Unfortunately this doesn't work well mainly because the
site's path name is in the project file and hence the
same for everybody.
As per David's suggestion I tried to set the site path to
whatever directory is used when opening the site. That
fixes the problem but I still have these questions :
1 - if the path coming from the project file is
overwritten why keep it in the file ?
I would like to remove it.
2 - if everybody can publish the site we will end up
having mess because the sitecopy state file is stored in
each user's home directory.
Possible solutions are :
- allow only a 'super-user' to publish a site
- store the sitecopy file in CVS and checkout/checkin
it each time an upload is done
- store the sitecopy file on the remote site and
retrieve/update it each time
Comments/suggestions/preferences are welcome !
Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
> 2 - if everybody can publish the site we will end up
> having mess because the sitecopy state file is stored in
> each user's home directory.
> Possible solutions are :
> - allow only a 'super-user' to publish a site
> - store the sitecopy file in CVS and checkout/checkin
> it each time an upload is done
> - store the sitecopy file on the remote site and
> retrieve/update it each time
> Comments/suggestions/preferences are welcome !
I think the first suggestion is best.
To allow any user to update the site, I think you will need to have some
kind of "passing the buck" mechanism; only the user which is holding "the
buck" can update the remote site.