You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Jamie <ja...@gmail.com> on 2006/03/27 21:12:05 UTC

web development revisited

Hi,

This is my first post here, and my first time using subversion. I am  
going to be setting up a system for web development. I have been  
researching this quite extensively, there seems to be no definitive  
setup for web development as yet so i thought I would come up with a  
system that is suitable to out working environment.

I have created a diagram to illustrate the system, this diagram is  
intended for non-technical people so please keep this in mind when  
commenting on it as it does contain some elements that are not quite  
technically correct.

diagram url: http://www.media72.co.uk/fabric.subversion.png

To start with the requirements for the system are:

- Easy to use
- No command line usage for day to-day-use
- Automated website updating (as far as possible)

The system I have come up with has 3 main branches of code:

- Development: for general development and bug fixes (short turn  
around work)
- Staging: for bug testing final code
- Live: live copy of code

There is also a 4th type of branch, this is for special projects.  
These are projects that will be developed over an extended period of  
time. Each time a new development project is needed a branch for this  
project will be created. When its finished it will be merged back  
into the development branch for deployment.

Developers will be able to checkout the development (or special  
project) branch of code to work on. Each time they commit their code  
a post-commit hook will be run that will perform a update to the  
development (or respective special project) website root.

Once development and testing has been finished on a particular  
project the development branch will be merged into the staging branch  
for a 2nd round of testing, after this it will be merged into the  
live branch for deployment to the live site.

The staging and live branches will not update the websites  
automatically, this will be performed through a web based interface.

I would appreciate any comments and feedback on this system, any  
problems you can see or anything that isn't possible with subversion.

I can see possible problems with the following issue:

- is it possible to have a post-commit hook run a different command  
depending on the branch thats being committed?

Cheers,
Jamie

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