[p4] Perforce Sync does not always work...
jo at mandarinconsulting.com
Thu Jul 27 12:12:06 PDT 2000
> We are considering sharing a single client (same workspace, mapped as a UNC
> path), between a small number of users, for occasional updates of an
> internal website. If users update the files locally, they either have to
> remember to update the webserver, or we could have a daemon update it, from
> the depot. On the one hand, it doesn't take much to implement the
> automated updates; on the other, if we shared a client, users wouldn't have
> to create a client and populate their machine. Could we run into problems
> if we share the client?
If it's the same area of disk, things will function fine. If
they're using the GUI, or even when they issue 'p4 opened',
things look a bit odd as you have different users with default
changelists. You can't actually submit someone else's
changelist by accident, so that part's OK.
If it was my choice, I'd use the apache web server plug-in to
get files from the depot for an intranet. You might want to
consider setting up a cron job to sync the "live" web workspace
instead. It's cleaner and easier to manage this way, IMO.
Hope all's going well,
Jo Woodison jo at mandarinconsulting.com +1 415 641 7989
~ mandarin consulting . san francisco . california . usa ~
More information about the perforce-user