Capistrano-Slug

Basically after a deploy is completed Capistrano packs up it's directory and sends it off for artifact deployment sometime else.

The initial use case is taking a point-in-time snapshot of Capistrano deployment, after every deployment, to use on newly bootstrapped servers.
When a new server bootstraps I want it to have the current code (and config etc) that was deployed by Capistrano without actually having to do a cap deploy.
This is achieved by downloading and 'installing' the slug on boot of a new server.

This enables things like automatic provisioning of new servers but still allows for Capistrano deployments.

Slug work happens on a single server only - the primary of the configured role (default :web).

Here's an example of capistrano-slug in use: https://gist.github.com/rjocoleman/11268563

Add this line to your application's Gemfile:

gem 'capistrano', '~> 3.2.0'
gem 'capistrano-slug'

And then execute:

$ bundle

Or install it yourself as:

$ gem install capistrano-slug

Require the module in your Capfile:

require 'capistrano/slug'

capistrano-slug comes with 4 tasks:

• slug
• slug:create
• slug:upload
• slug:clean

Create a slug and upload it to your configured storage.

$ cap production slug
 INFO Some stuff

Can be used during a deploy; if you want to create/upload a slug on every deploy:

# add to config/deploy.rb

after 'deploy:finished', :slug

Creates a slug:

$ cap staging slug:create
 INFO Slug: Successfully created foo-application-slug.tar.gz

Uploads a slug to your configured storage:

$ cap staging slug:upload
 INFO Slug: Uploaded foo-application-slug.tar.gz

Removes a slug from your server (not it's storage):

$ cap staging slug:clean
 INFO Slug: Cleaned foo-application-slug.tar.gz

Configurable options, shown here with defaults:

set :slug_role, :web
set :slug_name, -> { fetch(:application) }
set :slug_storage_backend, 's3'
set :slug_s3_bucket, nil

Currently only Amazon S3 is supported. Adding new storage backends shouldn't be a major task, I just haven't had the need - look at ./lib/capistrano/tasks/storage.rake and send a PR if you're interested!

An existing S3 bucket is required.

Credentials are not set anywhere in Capistrano, it's assumed you're using IAM instance profiles or have ENV vars set for credentials - if this isn't the case create an issue or send a PR!

The following configuration is required and must be set:

set :slug_s3_bucket, 'foo-slug-bucket'

Object uploads are set to the :private ACL and uploaded with server side encryption - they're not configurable I think these are sane options for this use case.

It currently relies on the aws cli being installed on the server: https://aws.amazon.com/cli/

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Add some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request