On Feb 12, 2008 7:17 PM, Ethan Schlenker <ethans_at_gamespot.com> wrote:
> Both the normal js file and the compressed file will be in svn. The
> compressed version will be also stored in svn so that our dev
> environment can use the compressed or the normal (to test if there are
> ever bugs with the compressed version). Devs don't have to touch the
> compressed version as the post-commit hook would take care of updating
> the compressed file when they commit changes to a normal file.
>
> > and worry about compression nearer
> > deployment. How do you deploy the javascript files? Could you use
> > something like Ant (ant.apache.org) and trigger the compression then?
>
> Doing it as part of the deployment process, is an option, but I'd like
> the compressed file to be in svn as well so that the dev environments
> can easily use it for testing. The more similar the live and dev
> enviroments are the better.
Why not use the same deployment process to update your development
environment as you use for the live environment (IOW, do the
"compression" when you put things out to the development environment
just like you would production)?
---------------------------------------------------------------------
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-13 02:50:40 CET