Re: Web Site Development and Trunk, Branches and Tags

Jay Smith wrote:
> Armed with my novice yet growing knowledge, I was thinking about
> treating the product web directory as working space and having an svn
> update script of some sort croned. The switch options sounds interesting
> though.

I strongly recommend you investigate post-commit hooks instead of cron
jobs. cron jobs do not take into effect any stability issues with a
given commit (i.e. you can't test first).

Among other things, you can have a hook that does different things:

1) all commits to trunk get automatically promoted to a test web server;
2) new tags get promoted to the production webserver (using switch).

> If I used the tags directory as the master for updates, where do
> developers committ to and update from? I'm guessing trunks (since tags
> is copy). My update process for production could watch either the trunk
> or the tags directory, but tags is better (faster more efficient)... is
> this correct?

Tags are the same as branches are the same as trunk. Using switch to
move from one tag to another is very efficient, though.

I specifically developed SVN::Notify::Mirror to facilitate exactly this
development model:

        http://search.cpan.org/search?query=SVN::Notify::Mirror

See the documentation for usage; I think it is pretty straightforward,
but if it isn't let me know where the confusion lies and I'll try and
clear it up... ;-)

John

p.s. also see SVN::Notify::Config (which I maintain, but did not
originally write) for an easy way to write the actual post-commit script:

        http://search.cpan.org/search?query=SVN::Notify::Config

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-02-25 15:34:51 CET