Faster deploy tool using tarballs and serf
Ruby
Latest commit cc038c0 Dec 19, 2016 @eagletmt eagletmt committed on GitHub Merge pull request #34 from eagletmt/debug-serf-event
Add debug log at sending Serf events
Permalink
Failed to load latest commit information.
bin Thor doesn't have `run` method Mar 19, 2014
docs
example
lib
misc
spec Fix before(:suite) warning Dec 19, 2016
.gitignore
.rspec rspec --init Feb 27, 2014
.travis.yml travis: disable sudo FTW Aug 28, 2015
Gemfile Let villein.gem path customizable Apr 30, 2014
LICENSE.txt Initial commit Feb 26, 2014
README.md Update README.md Nov 19, 2014
Rakefile
mamiya.gemspec

README.md

Mamiya - Faster deploy tool using tarballs and serf

Build Status

What's mamiya?

Mamiya allows you to deploy without ssh -- using tarballs, some storages (S3, etc), and Serf. Build application package on CI or somewhere, then distribute earlier (before you say "Deploy!"). You can switch to a new application quickly, when you're saying "deploy."

Mamiya uses similar directory structure with Capistrano 'deploy_to' -- you can try this easy.

Quick Start

See ./docs/quick_start.md.

Example configuration

example directory contains configuration files that work out-of-the-box. Try Mamiya in your local machine: foreman start

Problems in existing deploy tool

Existing major deploy tools (capistrano, mina, ...) use SSH to operate servers. But connecting to lot of servers via SSH makes deployment slow.

Mamiya solves such problem by using Serf and tarball on one storage (Amazon S3).

Also, I'm planning to allow to distribute files before the deploy command. I guess this can skip or shorten file transferring phase in deploy.

In the production

Misc.

Upgrade Notes

See docs/upgrading.md.

Contributing

  1. Fork it ( http://github.com/sorah/mamiya/fork )
  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