13 messages in com.perforce.perforce-user[p4] Re: Multiple users/same client?| From | Sent On | Attachments |
|---|---|---|
| Greg Spencer | 16 Nov 1999 14:28 | |
| Rob Juergens | 16 Nov 1999 14:47 | |
| Greg Spencer | 16 Nov 1999 15:01 | |
| Joan Yuen | 16 Nov 1999 15:25 | |
| Mike Meyer | 16 Nov 1999 15:30 | |
| Tony Sweeney | 16 Nov 1999 15:45 | |
| Stephen Vance | 16 Nov 1999 21:36 | |
| Rick Macdonald | 17 Nov 1999 00:55 | |
| PETERS MW Mr -NUCLEAR | 17 Nov 1999 06:06 | |
| Scott Blachowicz | 18 Nov 1999 09:45 | |
| Greg Spencer | 18 Nov 1999 10:28 | |
| Jeff A. Bowles | 18 Nov 1999 12:48 | |
| Mike Meyer | 18 Nov 1999 13:25 |
| Subject: | [p4] Re: Multiple users/same client? |
|---|---|
| From: | Greg Spencer (greg...@acm.org) |
| Date: | 11/18/1999 10:28:26 AM |
| List: | com.perforce.perforce-user |
With web sites, I would probably manage things so that each developer had their own client workspace to play around in, then the public web server site was just created via sync's from the Perforce depot. Each developer works in their own space and only checks things into the depot when it's "all done"...that way the public web site only gets sets of files that are deemed "all done" by the developers instead of intermediate stages of files.
Yes, this seems to be the "right" way to do it, and is the normal way I'd want to do it, but it means each developer needs to have a web server on their machine. Not too painful I guess, except that there is a possibility that the configration of their server and the staging server will be different. I thought about them using the checked in versions of the configuration file as well, but the configuration (it's Apache) contains the hostname and IP address of the server, so they'd need to have it constantly checked out to modify it for their own machine. Since that file doesn't really change all that often, it's probably a workable solution.
Thanks for the input everyone.
-Greg.