Versioning system for web development

Hello - I suppose this group could be suitable for my questions...

I am interested in a versioning system that works good for web authoring. I
don't know what differences web development might pose oon a versioning system,
but I have a feeling that it might.

First off - I already have a web project up and running with over 160 000 lines
of code. It is spread over a large hierarchy that mixes PHP documents with
images. The hierachy also contains files that are updated live by the web
server. I suppose I could seperate these succcessfully, to keep the PHP files
seperate from the rest...

But what kind of system is suitable, where I can handle different users having
access to different parts of the project?

Most importantly, these files and folders are constantly renamed and moved
around in the hierarchy along with the project growing in size. It need to be
able to handle those kind of things.

I am a Mac user, and my development environment of choice is BBEdit, which has
built in support for CVS (which doesn't seem to be to the task above) and
Perforce, which is a commercial system. Perforce is quite expensive, but I
suppose I could afford it if it did the above good.

I've looked at subversion as well, but I don't know how to determine if it's
suitable.


Anyone here using a versioning system for their web project and want to share
pros and cons?

--
Sandman[.net]

Sandman <mr@sandman.net> wrote:

> I've looked at subversion as well, but I don't know how to
> determine if it's suitable.

I'd recommend Subversion, since it tracks renames and moves quite
well. It has got hook support, enabling you to auto-update the
website as soon as commits are made. You could even set up your
webserver to watch those live-updated files you talk about, and
commit them to the Subversion server as soon as they change.

I think you can find out what you need to know about Subversion over
here:

http://svnbook.red-bean.com/

It is *the* reference manual for Subversion.

Regards,
Wald

In article <Xns95E8A34CF8E24arnoutstandaertnospa@134.58.127.1 2>,
wald <arnout.standaert@n*o_s-p%a|m.cit.kuleuven.ac.be> wrote:

> Sandman <mr@sandman.net> wrote:
>
> > I've looked at subversion as well, but I don't know how to
> > determine if it's suitable.
>
> I'd recommend Subversion, since it tracks renames and moves quite
> well. It has got hook support, enabling you to auto-update the
> website as soon as commits are made. You could even set up your
> webserver to watch those live-updated files you talk about, and
> commit them to the Subversion server as soon as they change.
>
> I think you can find out what you need to know about Subversion over
> here:
>
> http://svnbook.red-bean.com/
>
> It is *the* reference manual for Subversion.

Thanks, I'll look it up!

--
Sandman[.net]

On 2005-01-24, wald <arnout.standaert@n*o_s-p%a|m.cit.kuleuven.ac.be> wrote:
> Sandman <mr@sandman.net> wrote:
>
>> I've looked at subversion as well, but I don't know how to
>> determine if it's suitable.
>
> I'd recommend Subversion, since it tracks renames and moves quite
> well.

I'll just second that in case anyone cares ;)

I have no experience with commercial VC systems, but compared to CVS
it's bliss.

--
Regards,
- Jacob Atzen

On 24 Jan 2005 18:58:58 GMT, Jacob Atzen <jacob@aub.dk> wrote:

>On 2005-01-24, wald <arnout.standaert@n*o_s-p%a|m.cit.kuleuven.ac.be> wrote:
>> Sandman <mr@sandman.net> wrote:
>>
>>> I've looked at subversion as well, but I don't know how to
>>> determine if it's suitable.
>>
>> I'd recommend Subversion, since it tracks renames and moves quite
>> well.
>
>I'll just second that in case anyone cares ;)
>
>I have no experience with commercial VC systems, but compared to CVS
>it's bliss.

I'll third it. I tried CVS but didn't like the limitations. Everything about
Subversion seems to make sense.

--
Andy Hassall / <andy@andyh.co.uk> / <http://www.andyh.co.uk>
<http://www.andyhsoftware.co.uk/space> Space: disk usage analysis tool