A Gem For Capistrano Deployment Email Notification
| Project | CapistranoMailer |
|---|---|
| gem name | capistrano_mailer |
| license | MIT |
| expert support |  |
| download rank |  |
| version |  |
| dependencies |  |
| code quality |  |
| inline documenation |  |
| continuous integration |  |
| test coverage |  |
| homepage | on Github.com |
| documentation | on Rdoc.info |
| live chat |  |
| Spread |
🌏, 👼,  ,  , 🌹 |
- It is a Capistrano Plugin / Ruby Gem that requires ActionMailer
- It is MIT licensed
- It is old as duck, and it might be almost dead, maybe. (I started this project in 2007)
- rails2 branch, releases will be in 3.x range, requires Rails 2.X
- master branch, releases will be in 4.x range, requires Rails 3.X
- Requires at least Capistrano 2.4.3 (might work with capistrano as old as 2.1.0, but has not been tested)
- Known to be compatible with SCMs as of version 3.1.2: Perforce, SVN, and Git
- Known to be compatible with, but does not require, the deprec gem.
Ever wanted to be emailed whenever someone on the team does a cap deploy of trunk or some tag to some server. Wouldn't it be nice to know about it every time a release was deployed? For large rails projects this type of coordination is essential, and this plugin makes sure everyone on the need to know list is notified when something new is deployed.
This plugin/gem is an extension to Capistrano.
That means it registers itself with Capistrano as a plugin and is therefore available to call in your recipes.
If you are looking to roll your own email integration into capistrano then try this pastie: http://pastie.org/146264 (thanks to Mislav Marohnić). But if you want to take the easy road to riches then keep reading ;) -- figurative "riches" of course, I promise nothing in return for your using this plugin
The first time you deploy to a server (a 'cold' deploy) capistrano mailer will cause an error because it uses capistrano's previous release variables, and when there are no previous releases capistrano throws an error. In the next version this will be fixed, just don't have time at the moment. If you would like to work on this 'first deploy' problem please fork my repo and work on it!
Add this line to your application's Gemfile:
gem 'capistrano_mailer'
And then execute:
$ bundle
Or install it yourself as:
$ gem install capistrano_mailer
The 4.x+ versions of this gem require at least Rails 3
Switch to the rails2 branch (releases will be in 3.x range)
-
You need to have already setup capistrano in the project, including the 'capify .' command.
-
Add this line to the top of your config/deploy.rb:
You must make capistrano_mailer's libraries available in Ruby's load path. This is one way to do that:
$:.unshift 'vendor/plugins/capistrano_mailer/lib'
You must make capistrano_mailer's libraries available in Ruby's load path. This is one way to do that:
$:.unshift 'vendor/gems/capistrano_mailer-x.x.x/lib'
####################################
require 'capistrano/mailer' #configure capistrano_mailer:
The configuration file can go anywhere, but in past versions of the gem it was required to be in the config/ dir.
require 'config/cap_mailer_settings' ####################################
-
Configure Caistrano Mailer in the settings file required in step 2:
ActionMailer::Base.delivery_method = :smtp # or :sendmail, or whatever ActionMailer::Base.smtp_settings = { # if using :smtp :address => "mail.example.com", :port => 25, :domain => 'default.com', :perform_deliveries => true, :user_name => "[email protected]", :password => "mypassword", :authentication => :login } ActionMailer::Base.default_charset = "utf-8"# or "latin1" or whatever you are using
CapMailer.configure do |config| config[:recipient_addresses] = ["[email protected]"]
NOTE: THERE IS A BUG IN RAILS 2.3.3 which forces us to NOT use anything but a simple email address string for the sender address.
Therefore %("Capistrano Deployment" [email protected]) style addresses may not work in Rails 2.3.3
config[:sender_address] = "[email protected]" config[:subject_prepend] = "[EMPTY-CAP-DEPLOY]" config[:site_name] = "Empty Example.com App" end
-
Add these two tasks to your deploy.rb:
namespace :show do desc "Show some internal Cap-Fu: What's mah NAYM?!?" task :me do set :task_name, task_call_frames.first.task.fully_qualified_name #puts "Running #{task_name} task" end end
namespace :deploy do ...
desc "Send email notification of deployment (only send variables you want to be in the email)" task :notify, :roles => :app do show.me # this sets the task_name variable mailer.send_notification_email(self) end
... end
-
Make sure you've defined
rails_env,repository,deploy_to,host, andapplication.task_nameis defined by the show:me task above, and the others are defined behind the scenes by Capistrano! -
The only parameter to mailer.send_notification_email that is required is the first. Minimally you need to define the capistrano variables:
:rails_env :repository :task_name (provided by the show:me task included in this readme) :deploy_to :host :application
But there are tons of others - just take a look at lib/mailer/cap_mailer.rb.
If anyone has a cool way of recording the output into a capistrano accessible variable, so that it can be shoved into the release email that would be an excellent contribution!
-
Then add the hook somewhere in your deploy.rb:
after "deploy", "deploy:notify"
-
Enjoy and Happy Capping!
If you want to use your own views you'll need to recreate the notification_email view: First you need to define where your templates are:
CapMailer.configure_capistrano_mailer do |config|
config[:template_root] = "app/views/capistrano_mailer/"
end
Then you'll need to create templates there called:
notification_email.text.html.erb
and / or
notification_email.text.plain.erb
Take a look at the templates that comes with the plugin to see how it is done (views/cap_mailer/...)
Peter Boling (pboling) - Wrote original & maintainer Dave Nolan (textgoeshere) - lots of refactoring for 3.2 release Jason Rust (jrust) - Updated for Rails 3 compatibility
Thanks to Dustin Deyoung (ddeyoung) for the beautiful HTML email templates. Thanks to mixonix and Yoan Blanc (greut) for work on SCMs compatibility
Take a look at the reek list which is the file called REEK and stat fixing things. Once you complete a change, run the tests:
bundle exec rake test:all
If the tests pass refresh the reek list:
bundle exec rake reek > REEK
Follow the instructions for "Contributing" below.
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create new Pull Request
This library aims to adhere to Semantic Versioning 2.0.0. Violations of this scheme should be reported as bugs. Specifically, if a minor or patch version is released that breaks backward compatibility, a new version should be immediately released that restores compatibility. Breaking changes to the public API will only be introduced with new major versions.
As a result of this policy, you can (and should) specify a dependency on this gem using the Pessimistic Version Constraint with two digits of precision.
For example:
spec.add_dependency 'capistrano_mailer', '~> 0.5'
- MIT License - See LICENSE file in this project
- Copyright (c) 2008-2014 Peter H. Boling of Rails Bling
- Copyright (c) 2007-8 Peter Boling & Sagebit, LLC
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent