On Friday, October 07, 2011, Dalibor Karlović elucidated thus:
> Jan Keirse wrote:
> > Setting all that up shouldn't take very long.
>
> Yeah, for one site, but this would be like num_of_sites *
> num_of_people = ALOT. :)
Not really. We do it where I work. We have a single vhost, and the dev
ch
Dalibor Karlović schreef op 07/10/2011 14:15:39:
> Jan Keirse wrote:
>
> > Setting all that up shouldn't take very long.
>
> Yeah, for one site, but this would be like num_of_sites * num_of_people
=
> ALOT. :)
Not really. You need only one httpd.conf for all sites and people, with
only very
Jan Keirse wrote:
> Setting all that up shouldn't take very long.
Yeah, for one site, but this would be like num_of_sites * num_of_people =
ALOT. :)
> If you still don't want to do that I think your best bet would be to do
> everything related to subversion on the server, maintain the working c
Am 07.10.2011 11:09, schrieb Dalibor Karlović:
Actually, we've been working like that for years and it worked great as long
as the minor version of all the clients accessing it is the same, as soon as
the WC is upgraded, we all need to upgrade.
How we had it setup was up to now was:
- set perms
Dalibor Karlović schreef op 07/10/2011 11:09:08:
> Jan Keirse wrote:
>
> >> I don't know is this a Samba or Subversion (or my faulty config)
related
> >
> >> issue so I'll start here. I'd like to clarify that the need to have
just
> > one
> >> working copy (and not one per user on his/her loc
Jan Keirse wrote:
>> I don't know is this a Samba or Subversion (or my faulty config) related
>
>> issue so I'll start here. I'd like to clarify that the need to have just
> one
>> working copy (and not one per user on his/her local disk) is vital here.
>
> Can we know why?
Sure, I'll lay it ou
