BImA deployment rake task
Add this to your Gemfile:
group :development, :test do gem 'bima-deployment', git: 'https://github.com/jdahlke/bima-deployment.git', tag: '2.0.3' end
$ bundle exec rails g bima_deployment:install NAME
you generate a
config/deployment.yml file via the Rails generator process.
NAME is used for OpsWorks stack and app names in different ways:
- Stack names will be
NAME (Staging)for development and staging environments,
NAME (Production)for the production environment.
- App names will be
name_stagingfor development and staging environments respectively,
namefor the production environment.
--notificationcan be either
falseto specify whether you want to be notified after a successful deployment to production environments. Default:
--slackprovides the URI to your Slack Incoming WebHook.
--strategyshould be either
opsworks/s3to specify your deployment strategy. Default:
$ bundle exec rails g bima_deployment:install MyApp \ --slack=https://hooks.slack.com/services/URI/to/my/webhook \ --strategy=opsworks/git
bundle exec rake deploy[TAG_OR_BRANCH_NAME]to deploy your code to AWS. As the
opsworks/s3strategy requires uploading a sizable file to S3 first, this process can take a while.
- Get a cup of tea (or coffee) and watch your code being deployed to AWS for you.
Note: Credentials for AWS related operations are automagically loaded from
The rake taks will try to read credentials from a profile
[bima]. If it fails, it will fallback to
Note: If git_tag is not provided, this will deploy the currently checked out revision (HEAD), not master.
git_ref of your repository to your AWS OpsWorks development stack.
git_ref of your repository to your AWS OpsWorks production stack.
git_ref of your repository to your AWS OpsWorks staging stack.
Creates a working copy of
git_ref of your repository in
packs it into a
.tbz2 file in
tmp/releases. Uploads the release file for
git_ref to S3.
Cleans up the