RE: Re: Web Hosting using subversion

> -----Original Message-----
> From: John Peacock [mailto:john.peacock@havurah-software.org]
>
> Bicking, David (HHoldings, IT) wrote:
> > 1. checkout code to a local workspace known by a local web
> server 2.
> > make whatever changes are necessary.
> > 3. test until blue in the face.
> > 4. commit changes.
> > 5. backup the live site. Clear the live site.
> > 6. Export the workspace to the live site.
> > 7. Smoke test the live site.
>
> Argh. That is so needlessly complicated and prone to human
> error (especially step #5 in my experience). Install my
> modules SVN::Notify::Mirror[1] and SVN::Notify::Config[2] and
> use something like the following post-commit file:

Interesting. To me, most of the above is easilly scriptable. The
developer only really cares about steps 1 - 4, which is just standard
practice (you _do_ test your work before you commit, right?). Basic
deployment practices that I use are scripted via (N)Ant, so 5 and 6 are
automated. 7 is (once again) a standard practice. Of course, when
deploying to a test server, you don't even need 5 and 6, you just use a
simple post-commit script to export the new version to the test site.
Neither complicated, nor more prone to human error than anything else.

I was describing a workflow. Your solution appears to me to be a
specific implementation of that workflow, and in fact is more
complicated because you added email and such to the mix. Since you
already implemented it for us, it is simple for us - kudos. However, in
my shop, I doubt they'd permit me to install Perl on our Windows server.

--
David
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information.  If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited.  If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org