[nycphp-talk] Webserver file access (and version control)
greg.rundlett at gmail.com
Tue Aug 21 21:53:06 EDT 2007
I wanted to add a few cents about the role of a version control system
in managing websites.
Release Engineering is a complex subject worthy of it's own
profession. I say that because I've worked in a Release Engineering
team supporting multiple software products and distributed teams
numbering in the hundreds. If you have complex software that you need
to release or distribute, then you will invariably use tools like
Phing, Ant etc.
That said, releasing website code, even 'application' code can easily
be handled by using a 'working copy' checkout from a Subversion
repository. I would consider it 'good form' to use this approach. In
fact this makes it incredibly easy to release code through dev to
staging to production. And it is easy to revert (with or without
tags). Tags are just a convenience (and generally recommended when
you have an actual QA or test process.)
For people using this approach, do an 'svn status -u' to show what
would be updated prior to doing an 'svn up'.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
More information about the talk