Dalibor Karloviæ <dado_at_burza.hr> 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 local disk) is vital
here.
> >
> > Can we know why?
>
> Sure, I'll lay it out:
> - we're a small web development studio
> - we have a development server which exposed one share to the team via
Samba
> - if we're developing a new site called foo.com, we create a working
copy on
> the server and make it available as foo.com.web in our local domain
which
> makes it accessible from each workstation right away
> - this gives us a point to which anybody working on the site can hook up
to
> and we all can see exactly what's going on at any point in time
> - also, the less tech-savy guys/gals (designers, copywriters, PMs) don't
> need to setup their own entire work environment (server, database,
virtual
> hosts, etc), they just open the share and a browser and start working.
> - we cannot automate the procedure because there's alot of different
systems
> on staff (WinXP, Win7, MacOSX, Fedora, Ubuntu, etc).
>
> The one "working copy per user" has too high of a (time) cost here.
I don't think it should be a lot of work to set it up to work with local
sandboxes:
* make a project containing the apache config files for the various
platforms. That way you only have to create them once for each platform,
and most parts of that will largely be copies.
* standardize paths: ie everything should go under either c:\www or /www,
so that config files don't need to be modified.
Developers just go to foo.localhost instead of foo.com.web. You can do an
automatic checkout of what's committed to foo.com.web to show what's under
development.
Setting all that up shouldn't take very long.
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 copy
on the server, do all commits from there. You can still access the working
copy from Samba to do the actual coding, just don't commit anything from
windows.
Kind Regards,
JAN KEIRSE
ICT-DEPARTMENT
Software quality & Systems: Software Engineer
**** DISCLAIMER ****
http://www.tvh.com/newen2/emaildisclaimer/default.html
"This message is delivered to all addressees subject to the conditions
set forth in the attached disclaimer, which is an integral part of this
message."
Received on 2011-10-07 11:26:28 CEST