[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Question RE subversion (web)projects setup

From: Simon <greminn_at_gmail.com>
Date: 2007-08-14 11:54:39 CEST

Hi There,

Im pretty new to subversion but getting the hang of it. I have a setup
that we have got going which i would like to get some feedback on and
also ask a specific question please?

We have several web developers inhouse and a few outhouse. We have
subversion setup in a testing environment for a small project to test.
All users are using Zend Studio using https/webdav to
checkout/update/commit files.

Inhouse users have a personal directory which their checked out files
go on the (local/debian) web server (edited over a samba link): eg:
/home/userA/projectA, /home/userB/projectA, etc Then they can get to
this via apache thus: http://projectA.userA.domain.com/, etc for
testing their changes etc.

Outhouse users have a similar setup, but using debian on vmware on
their local workstation for personal testing.

Then we have setup /home/development/ directory, checked out the
project, then a post-commit hook does a svn update on. This seems to
work well (at this stage). The clients can get to the "projectA"
project via: http://projectA.dev.domain.com/ to test finalised
development sites.


1). What is wrong with this? :)

2). We have a nice little sub 1MB project as projectA, im concerned
when we then go to load in a couple of GB's of projectB, C, D etc..
what will happen here?

3). Further to above... should we be having separate "subversion's"
for projects rather than lump them all together?

Sorry if my terminology is not quite right, but helpful hints and
suggestions are very welcome. We all LIKE what we see so far!!



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Aug 14 11:52:43 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.