This is a rsync 'scm' for Capistrano v3, drastically improving deployment performance, and avoiding you to install git on production servers. This was originally a fork of capistrano-rsync.

Capistrano deployment from an archive on Amazon S3.

Capistrano deployment strategy that creates and pushes a tarball into S3, for both pushed deployments and pulled auto-scaling.

Capistrano plugin that ensures the `deploy_to` deployment path exists and has the right permissions.

Capistrano 3.x plugin to deploy Jenkins artifacts.

Sentry release/deployment integration

Shoryuken integration for Capistrano

Capistrano Plugin to control services by systemd

Capistrano notifications for all team members via OSX Notification Center

A capistrano 3 plugin that aids in rendering erb templates and uploads the content to the server if the file does not exists at the remote host or the content did change

Capistrano 3.x tasks to upload shared config that is stored outside of SCM

Capistrano with rsync

Minimalist Capistrano 2 notifier for Slack.

Capistrano recipes to assist with development, testing, & deployment of SUL/DLSS Ruby projects

Helps you automatically create tags for each stage in a multi-stage deploment and deploy from the latest tag from the previous environment

Capistrano plugin for deploying to Amazon EC2 instances by security groups.

Capistrano 3.x plugin that integrates Unicorn server tasks.

A set of optional extensions to capistrano to make common tasks easier.

A set of optional extensions to capistrano to make common tasks easier.

The rubber plugin enables relatively complex multi-instance deployments of RubyOnRails applications to Amazon's Elastic Compute Cloud (EC2). Like capistrano, rubber is role based, so you can define a set of configuration files for a role and then assign that role to as many concrete instances as needed. One can also assign multiple roles to a single instance. This lets one start out with a single ec2 instance (belonging to all roles), and add new instances into the mix as needed to scale specific facets of your deployment, e.g. adding in instances that serve only as an 'app' role to handle increased app server load.