Website managment using SubVersion

[Stefan <st...@gmx.net>]

Hi,

I would like to use SubVersion for the following problem, I have never
used it before:

I would like SubVersion to manage a website with several developers,
there should be some branches, stable, testing and probably some older
one, with about 10 users having access to testing and 3 to stable, so
you always commit to testing, when it works correctly this change is
copied to stable by one of these 3 persons.
I would really prefer that over ftp, because here you directly see who
changed what, step back, you cannot replace files someone else has
updated already, etc.

So far it´s probably quite simple, but: How do I access to the branches
like in normal file system? I have a Apache 2 Server with PHP on Debian,
how is it possible to use a svn-repository as a document (and of course
also PHP-files) source?

I would like to have, svn should not be visible to normal website visitor:
www.example.com -> stable branch
testing.example.com -> testing branch

Any idea how I could do that with optimal performance?

Thank you,
Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

RE: Website managment using SubVersion

[Jim Priest <ji...@clickculture.com>]

> -----Original Message-----
> From: Stefan [mailto:stefan-oltmanns@gmx.net] 

> I would like to use SubVersion for the following problem, I 
> have never used it before:

Stephan - I'm just getting started using Subversion for web development as
well. I'd suggest downloading it and trying it out on a small project - I
read the book but the best way to learn how/what it does is to jump in IMO.

> I would like to have, svn should not be visible to normal 
> www.example.com -> stable branch
> testing.example.com -> testing branch

This is certainly doable I think. Right now in our setup - each developer is
setup to work on their own PC's. When they commit changes back to the
repository - I have a script on our development server they can kick off and
it does an update which pulls all the latest changes from the repo to the
server. There is no FTP involved. I'm going to roll out the same thing (in a
more secure manner) for our production server.  The benefit of this is if
something should go wrong I should be able to revert back to a previous
version pulled from the repository.

Right now I'm struggling with a new situation - we have a client site where
the client wants to edit some files - so I'm trying to figure out how best
to get those changes BACK into our repo - but that's another topic.

Jim



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org