Project

blessing

0.0
Repository is archived
No commit activity in last 3 years
No release in over 3 years
blessingborgand/blessingHomepageDocumentationSource CodeBug TrackerWiki
A group of Unicorns is called a blessing. Blessing gem provides an easy way to manage multiple Unicorn! Rack servers.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
9,447
Stars
1
Forks
0
Watchers
2
 Releases
Current version
1.0.1
Total releases
2
First release
2011-10-18
Latest release
2011-11-04
 Issues
Open Issues
3
Closed Issues
1
Total Issues
4
Issue Closure Rate
25%
 Development
Primary Language
Ruby
Average date of last 50 commits
2011-10-13
Reverse Dependencies
0

 Dependencies

Development

bundler
~> 1.0.0
jeweler
~> 1.6.0
rcov
>= 0
rspec
~> 2.3.0

Runtime

daemons
>= 0
unicorn
>= 0
 Project Readme

blessing¶ ↑

A group of Unicorns is called a blessing.

Blessing is a script to manage multiple Unicorn Rack servers.

Install¶ ↑ 

gem install blessing

Run¶ ↑

Blessing CLI script takes at least one argument, which provides a list of Unicorn configuration files and then starts Unicorn instances from them.

blessing /var/www/rails_app/config/unicorn.conf

blessing /var/www/*/config/unicorn.conf

blessing /var/vhosts/**/config/unicorn.conf

After starting the servers, Blessing keeps monitoring the given list of configurations and reacts to the following events:

  • when a conf file is changed, restarts the corresponding Unicorn instance

  • when a new conf is found (via globbing), starts a new instance

  • when a conf is removed, stops the corresponding instance

Signalling¶ ↑

Blessing reacts to the following signals:

  • INT, TERM - shut down Blessing group gracefully

  • USR1 - immediately rerun verification cycle

  • USR2 - try to resurrect dead Unicorns

Contributing to blessing¶ ↑

  • Check out the latest master to make sure the feature hasn’t been implemented or the bug hasn’t been fixed yet

  • Check out the issue tracker to make sure someone already hasn’t requested it and/or contributed it

  • Fork the project

  • Start a feature/bugfix branch

  • Commit and push until you are happy with your contribution

  • Make sure to add tests for it. This is important so I don’t break it in a future version unintentionally.

  • Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.

Copyright¶ ↑

Copyright © 2011 Laas Toom. See LICENSE.txt for further details.