Hello-
I've built a deployment strategy to plug into capistrano so that
deployments go through an S3 bucket.
Properties:
- Expects a deploy_bucket it can read from and write to
- Uses configuration[:s3_config] to find creds
- Names releases {application}_{revision}.tgz
- Looks in the bucket for a file with that name - skip to actual
deployment if found
- Checks out the specified revision, bundles it up, and pushes to the
S3 bucket
It's useful for situations (like mine) where you:
- Deploy from a spot close to your svn
- Don't want to expose the svn repository to the managed servers (and
the whole web)
- Want later servers to get quick access to the code package
- Deploy from behind a cable modem (slow) to EC2 instances (with fast
access to S3)
I put the file (s3_bucket.rb just uploaded to the group) in my cap
project directory, to in effect monkey-patch a new deploy strategy for
capistrano without touching the capistrano gem. (Full path lib/
capistrano/recipes/deploy/strategy/s3_bucket.rb, with the lib
directory in the same directory as Capfile and config)
Feedback is much appreciated ... I'd love to see this folded into a
future version of capistrano.
-Bill Kirtley
--~--~---------~--~----~------------~-------~--~----~
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/capistrano
-~----------~----~----~----~------~----~------~--~---
