On 2 Mar 2011, at 17:27, Pedro Melo wrote:
On Wed, Mar 2, 2011 at 5:24 PM, Tomas Doran <[email protected]>
wrote:
Installing to production servers via rsync / unison is insane, as
there is
exactly no way of knowing what version the production server is on,
with
what bugs...
Of course you can. You can include a file .version at the root created
with 'git describe --always' > .version before you rsync, and then
include it on your test reports.
Rsync is a valid deployment method, specially if you use a stage
server where you make install you app.
Ah, but then you're deploying a specific sha1 from git, rather than
just rsyncing a directory!
And as you'll have a script to ensure that you have reset --hard
MYSHA1 (otherwise you are perfectly screwed just as I described), then
you can put the build parts in there...
Cheers
t0m
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
