mina 0.1.0

data/.gitignore

@@ -0,0 +1,4 @@
+doc
+test_env/deploy
+.rvmrc
+Gemfile.lock

data/.rspec

@@ -0,0 +1 @@
+-c --order rand -t ~ssh

data/.travis.yml

@@ -0,0 +1,13 @@
+language: ruby
+rvm:
+ - 1.8.7
+ - 1.9.3
+ - rbx-18mode
+ - rbx-19mode
+ - ruby-head
+env:
+ - "rake=0.8"
+ - "rake=0.9"
+script: "bundle exec rspec"
+notifications:
+  email: false

data/Gemfile

@@ -0,0 +1,10 @@
+# Why use bundler?
+# Well, not all development dependencies install on all rubies. Moreover, `gem
+# install mina --development` doesn't work, as it will also try to install
+# development dependencies of our dependencies, and those are not conflict free.
+# So, here we are, `bundle install`.
+
+source :rubygems
+gemspec
+
+gem 'rake', "~> #{ENV['rake'] || "0.9"}.0"

data/HISTORY.md

@@ -0,0 +1,148 @@
+v0.1.0 - Jun 06, 2012
+---------------------
+
+Renamed to Mina from Van Helsing.
+
+
+v0.0.1.pre7 - Jun 06, 2012
+--------------------------
+
+### Added:
+  * __`vh rails[command]` and `vh rake[command]` tasks.__
+  * __Add `vh run`.__
+  * `-S` as an alias for `--simulate`.
+  * the `#set_default` helper.
+  * the `bundle_prefix` setting.
+  * New `term_mode` setting.
+
+### Changed:
+  * `--simulate` show things without the `ssh` command or shellescaping.
+
+v0.0.1.pre6 - Jun 06, 2012
+--------------------------
+
+Thanks to @sosedoff for his contributions that made it to this release.
+
+### Added:
+  * __Rubinius support.__
+  * __Ruby 1.8 support.__
+  * Prelimenary JRuby support.
+  * MIT license.
+  * Highlight errors as red in deploy.
+  * Use popen4 instead of popen3. Support JRuby via IO.popen4.
+
+### Changed:
+  * __Rename `to :restart` to `to :launch`.__
+  * __Make deploys fail if renaming the build (eg, not setup properly) fails.__
+
+### Tests:
+  * Added `rake spec` (aliased as just `rake`) task. It tests with Rake 0.8 and 0.9 both.
+  * Integrate with [Travis CI](http://travis-ci.org).
+  * Make the SSH test more portable.
+  * Removed `rake spec:verbose`.
+
+v0.0.1.pre5 - Jun 05, 2012
+--------------------------
+
+### Added:
+  * Add `--trace` to the `vh help` screen.
+  * Rake 0.8 compatibility.
+  * Ruby 1.8.7 compatibility.
+
+### Changed:
+  * Use `:domain` instead of `:host`.
+
+### Misc:
+  * Allow rake 0.8 testing using `rake=0.8 rspec`.
+  * Add more README examples.
+
+v0.0.1.pre4 - Jun 05, 2012
+--------------------------
+
+### Added:
+  * `--simulate` switch.
+  * `--verbose` switch.
+  * The help screen now shows command line switches (like `--verbose`).
+  * Build in `tmp/` instead of in `releases/`.
+  * Use `verbose_mode` and `simulate_mode` instead. Using 'verbose' causes
+    problems.
+  * New `#deploy_script` helper, to make things more transparent.
+
+### Misc:
+  * Added a test for an actual deployment.
+  * Make the `test_env` runnable even without a net connection.
+  * New tests for actual deployment. Just do `rspec -t ssh`.
+  * Cleanup `git:clone` code.
+  * A buncha code cleanups.
+
+v0.0.1.pre3 - Jun 04, 2012
+--------------------------
+
+### Added:
+  * A help screen. You can see it with `vh --help`, `vh -h` or just plain `vh`.
+  * Implemented `vh --version`.
+  * Sequential release versions. Yay!
+  * Added the `build_path` setting, which supercedes the now-removed `release_path`.
+
+### Removed:
+  * `release_path` has been deprecated.
+
+### Fixed:
+  * Stupid critical bug fix: fix `vh:setup` giving the world access to deploy_to.
+  * Ensure that SSH stderr output is shown properly.
+  * Make `#invoke` work with tasks with arguments (eg, :'site:scrape[ensogo]')
+
+### Changed:
+  * Edit the default deploy.rb to have a description for the deploy task.
+  * Make `vh -T` show `vh` instead of `rake`.
+  * Make `vh setup` ensure ownership of the `deploy_to` path.
+  * Make deploy steps more explicit by echoing more statuses.
+  * When deploys fail, you now don't see the default Ruby backtrace. It now
+    behaves like Rake where you need to add `--trace` to see the trace.
+
+### Misc:
+  * Fixed the error that sometimes happens when invoking `vh` without a deploy.rb.
+  * Update the sample deploy.rb file to be more readable.
+  * The *test_env/* project can now be deployed without problems, so you can try
+    things out.
+  * Lots of new tests.
+  * rspec test order is now randomized.
+  * rspec output is colored (thanks to .rspec).
+  * Better script indentation when running in simulation mode.
+  * In symlinking `./current/`, use `ln -nfs` instead of `rm -f && ln -s`.
+
+v0.0.1.pre2 - Jun 03, 2012
+--------------------------
+
+### Added:
+  * Implement `vh init` which creates a sample *deploy.rb*.
+  * Implement 'vh setup'.
+  * Added the configurable `:releases_path` setting, so you may change where to keep releases.
+  * Added documentation via Reacco.
+  * Allow settings to throw errors on missing settings by adding a bang (e.g.,
+    `bundle_path!` or `settings.bundle_path!`)
+
+### Changed:
+  * Allow `bundle:install` to skip having shared bundle paths if `:bundle_path` is set to nil.
+  * Rename `force_unlock` to `deploy:force_unlock`.
+  * Rename `vh:link_shared_paths` to `deploy:link_shared_paths`.
+  * Invoking `deploy:force_unlock` now shows the command it uses.
+
+### Fixed:
+  * The `bundle:install` task now honors the `bundle_path` setting.
+  * Fixed `deploy:force_unlock` always throwing an error.
+  * The `deploy:force_unlock` task now honors the `lock_file`
+    setting, so the user may change the location of the lock file.
+  * Fixed `rails:assets_precompile` not compiling if no older assets found.
+
+### Removed:
+  * Deprecate `#validate_set`.
+
+### Other things:
+  * Move deploy settings to deploy.rb.
+  * Rename the `default` addon to `deploy`.
+
+v0.0.1.pre1 - Jun 02, 2012
+--------------------------
+
+Initial version.

data/LICENSE

@@ -0,0 +1,23 @@
+LICENSE
+
+The MIT License
+
+Copyright (c) 2012 Nadarei, Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,620 @@
+# Mina [![status](https://secure.travis-ci.org/nadarei/mina.png?branch=master)](http://travis-ci.org/nadarei/mina)
+
+Really fast deployer and server automation tool.
+
+Mina works really fast because it's a deploy Bash script generator. It
+generates an entire procedure as a Bash script and runs it remotely in the
+server.
+
+Compare this to the likes of Vlad or Capistrano, where each command
+is ran separately on their own SSH sessions. Mina only creates *one* SSH
+session per deploy, minimizing the SSH connection overhead.
+
+    $ gem install mina
+
+Features
+--------
+
+* __Really fast.__ Mina only makes one SSH connection per deploy. It
+  builds a Bash script and executes it remotely, reducing the overhead of
+  creating SSH connections to do processing locally (like Vlad or Capistrano
+  does).
+
+* __Safe deploys.__ New releases are built on a temp folder. If the deploy
+  script fails at any point, the build is deleted and it'd be as if nothing
+  happened.
+
+* __Locks.__ Deploy scripts rely on a lockfile ensuring only one deploy can
+  happen at a time.
+
+* __Works with anything.__ While Mina is built with Rails projects it
+  mind, it can be used on just about any type of project deployable via SSH,
+  Ruby or not.
+
+* __Built with Rake.__ Setting up tasks will be very familiar! No YAML files
+  here. Everything is written in Ruby, giving you the power to be as flexible in
+  your configuration as needed.
+
+Setting up a project
+--------------------
+
+Let's deploy a project using Mina.
+
+### Step 1: Create a config/deploy.rb
+
+In your project, type `mina init` to create a sample of this file.
+
+This is just a Rake file with tasks!
+
+    $ mina init
+    Created config/deploy.rb.
+
+See [About deploy.rb](#about_deployrb) for more info on what *deploy.rb* is.
+
+### Step 2: Set up your server
+
+Make a directory in your server called `/var/www/flipstack.com` (in *deploy_to*)
+change it's ownership to the correct user.
+
+    # SSH into your server, then:
+    $ mkdir /var/www/flipstack.com
+    $ chown -R username /var/www/flipstack.com
+
+    # Make sure 'username' is the same as what's on deploy.rb
+
+### Step 3: Run 'mina setup'
+
+Now do `mina setup` to set up the [folder structure](#directory_structure) in this
+path. This will connect to your server via SSH and create the right directories.
+
+    $ mina setup
+    -----> Creating folders... done.
+
+See [directory structure](#directory_structure) for more info.
+
+### Step 4: Deploy!
+
+Use `mina deploy` to run the `deploy` task defined in *config/deploy.rb*.
+
+    $ mina deploy
+    -----> Deploying to 2012-06-12-040248
+           ...
+           Lots of things happening...
+           ...
+    -----> Done.
+
+Command line options
+--------------------
+
+* `--verbose` - This will show commands being done on the server. Off by
+  default.
+
+* `--simulate` - This will not invoke any SSH connections; instead, it will
+  simply output the script it builds.
+
+About deploy.rb
+---------------
+
+The file `deploy.rb` is simply a Rakefile invoked by Rake. In fact, `mina` is
+mostly an alias that invokes Rake to load `deploy.rb`.
+
+As it's all Rake, you can define tasks that you can invoke using `mina`. In this
+example, it provides the `mina restart` command.
+
+``` ruby
+# Sample config/deploy.rb
+set :domain, 'your.server.com'
+
+task :restart do
+  queue 'sudo service restart apache'
+end
+```
+
+The magic of Mina is in the new commands it gives you.
+
+The `queue` command queues up Bash commands to be ran on the remote server.
+If you invoke `mina restart`, it will invoke the task above and run the queued
+commands on the remote server `your.server.com` via SSH.
+
+See [the command queue](#the_command_queue) for more information on the *queue*
+command.
+
+The command queue
+-----------------
+
+At the heart of it, Mina is merely sugar on top of Rake to queue commands
+and execute them remotely at the end.
+
+Take a look at this minimal *deploy.rb* configuration:
+
+``` ruby
+set :user, 'john'
+set :domain, 'flipstack.com'
+
+task :logs do
+  queue 'echo "Contents of the log file are as follows:"'
+  queue "tail -f /var/log/apache.log"
+end
+```
+
+Once you type `mina logs` in your terminal, it invokes the *queue*d commands
+remotely on the server using the command `ssh john@flipstack.com`.
+
+```
+# Run it in simulation mode so we see the command it will invoke:
+$ mina logs --simulate
+(
+  echo "Contents of the log file are as follows:"
+  tail -f /var/log/apache.log
+) | ssh john@flipstack.com -- bash -
+```
+
+Subtasks
+--------
+
+Mina provides the helper `invoke` to invoke other tasks from a
+task.
+
+```ruby
+task :down do
+  invoke :maintenance_on
+  invoke :restart
+end
+
+task :maintenance_on
+  queue 'touch maintenance.txt'
+end
+
+task :restart
+  queue 'sudo service restart apache'
+end
+```
+
+In this example above, if you type `mina down`, it simply invokes the other
+subtasks which queues up their commands. The commands will be ran after
+everything.
+
+Deploying
+---------
+
+Mina provides the `deploy` command which *queue*s up a deploy script for
+you.
+
+``` ruby
+set :domain, 'flipstack.com'
+set :user, 'flipstack'
+set :deploy_to, '/var/www/flipstack.com'
+set :repository, 'http://github.com/flipstack/flipstack.git'
+
+task :deploy do
+  deploy do
+    # Put things that prepare the empty release folder here.
+    # Commands queued here will be ran on a new release directory.
+    invoke :'git:clone'
+    invoke :'bundle:install'
+
+    # These are instructions to start the app after it's been prepared.
+    to :launch do
+      queue 'touch tmp/restart.txt'
+    end
+
+    # This optional block defines how a broken release should be cleaned up.
+    to :clean do
+      queue 'log "failed deployment"'
+    end
+  end
+end
+```
+
+It works by capturing the *queue*d commands inside the block, wrapping them
+in a deploy script, then *queue*ing them back in.
+
+How deploying works
+-------------------
+
+Here is an example of a deploy! (Note that some commands have been simplified
+to illustrate the point better.)
+
+### Step 1: Build it
+
+The deploy process builds a new temp folder with instructions you provide.
+In this example, it will do `git:clone` and `bundle:install`.
+
+```
+$ mina deploy --verbose
+-----> Creating the build path
+       $ mkdir tmp/build-128293482394
+-----> Cloning the Git repository
+       $ git clone https://github.com/flipstack/flipstack.git . -n --recursive
+       Cloning... done.
+-----> Installing gem dependencies using Bundler
+       $ bundle install --without development:test
+       Using i18n (0.6.0)
+       Using multi_json (1.0.4)
+       ...
+       Your bundle is complete! It was installed to ./vendor/bundle
+```
+
+### Step 2: Move it to releases
+
+Once the project has been built, it will be moved to `releases/`. A symlink
+called `current/` will be created to point to the active release.
+
+```
+-----> Moving to releases/4
+       $ mv "./tmp/build-128293482394" "releases/4"
+-----> Symlinking to current
+       $ ln -nfs releases/4 current
+```
+
+### Step 3: Launch it
+
+Invoke the commands queued up in the `to :launch` block. These often
+commands to restart the webserver process. Once this in complete, you're done!
+
+```
+-----> Launching
+       $ cd releases/4
+       $ sudo service nginx restart
+-----> Done. Deployed v4
+```
+
+### What about failure?
+
+If it fails at any point, the release path will be deleted. If any commands are
+queued using the `to :clean` block, they will be ran. It will be as if nothing
+happened.
+
+```
+# Lets see what happens if a build fails:
+-----> Launching
+       $ cd releases/4
+       $ sudo service nginx restart
+       Starting nginx... error: can't start service
+-----> ERROR: Deploy failed.
+-----> Cleaning up build
+       $ rm -rf tmp/build-128293482394
+-----> Unlinking current
+       $ ln -nfs releases/3 current
+       OK
+```
+
+Directory structure
+-------------------
+
+The deploy procedures make the assumption that you have a folder like so:
+
+    /var/www/flipstack.com/     # The deploy_to path
+     |-  releases/              # Holds releases, one subdir per release
+     |   |- 2012-06-12-838948
+     |   |- 2012-06-23-034828
+     |   '- ...
+     |-  shared/                # Holds files shared between releases
+     |   |- logs/               # Log files are usually stored here
+     |   `- ...
+     '-  current/               # A symlink to the current release in releases/
+
+It also assumes that the `deploy_to` path is fully writeable/readable for the
+user we're going to SSH with.
+
+Configuring settings
+--------------------
+
+Settings are managed using the `set` and `settings` methods. This convention is
+inspired by Sinatra and Vlad.
+
+``` ruby
+set :version, "v2.0.5"
+
+settings.version    #=> "v2.0.5"
+settings.version?   #=> true
+```
+
+You can also retrieve settings without the `settings.` prefix.
+
+``` ruby
+set :version, "v2.0.5"
+
+version    #=> "v2.0.5"
+version?   #=> true
+```
+
+### Dynamic values
+
+You can also give settings using a lambda. When the setting is retrieved, it
+will be evaluated.
+
+``` ruby
+set :tag, lambda { "release/#{version}" }
+set :version, "v2.0.5"
+
+tag    #=> "release/v2.0.5"
+```
+
+### Inside and outside tasks
+
+All of these are accessible inside and outside tasks.
+
+``` ruby
+set :admin_email, "johnsmith@gmail.com"
+
+task :email do
+  set :message, "Deploy is done"
+
+  system "echo #{message} | mail #{admin_email}"
+end
+```
+
+### Validations
+
+If you would like an error to be thrown if a setting is not present, add a bang
+at the end.
+
+``` ruby
+task :restart do
+  queue "#{settings.nginx_path!}/sbin/nginx restart"
+end
+
+# $ mina restart
+# Error: You must set the :nginx_path setting
+```
+
+Defaults
+--------
+
+There are a few deploy-related tasks and settings that are on by default.
+
+### Base settings
+
+* `verbose_mode` - True if the `--verbose` flag is on, false otherwise. Used to
+  signal if commands are to be shown.
+
+* `simulate_mode` - True if `--simulate` flag is on, false otherwise. Used to
+  signal if no SSH connections are to be made, and the scripts will just be
+  printed locally.
+
+* `term_mode` - If set to `:pretty`, prettifies the output with indentations.
+  (Default with deploys.)
+
+### SSH settings
+
+* `domain` - Hostname to SSH to. *Required.*
+
+* `user` - Username to connect to SSH with. Optional.
+
+* `identity_file` - Local path to the SSH key to use. Optional.
+
+``` ruby
+# Example:
+set :domain, 'flipstack.me'
+set :user, 'flipstack_www'
+set :identity_file, 'flipstack.pem'
+```
+
+### Deploy settings
+
+* `deploy_to` - Path to deploy to. *Required.*
+
+* `releases_path` - The path to where releases are kept. Defaults to
+  `releases`.
+
+* `shared_path` - Where shared files are kept. Defaults to
+  `shared`.
+
+* `current_path` - The path to the symlink to the current release. Defaults to
+  `current`.
+
+* `lock_file` - The deploy lock file. A deploy does not start if this file is
+  found. Defaults to `deploy.lock`.
+
+
+``` ruby
+# Example:
+set :deploy_to, '/var/www/flipstack.me'
+set :releases_path, 'releases'
+set :shared_path, 'shared'
+set :current_path, 'current'
+set :lock_file, 'deploy.lock'
+
+# This means the following paths will be
+# created on `mina setup`:
+#    /var/www/flipstack.me/
+#    /var/www/flipstack.me/releases/
+#    /var/www/flipstack.me/shared/
+```
+
+### Task - setup
+
+Prepares the `deploy_to` directory for deployments. Sets up subdirectories and
+sets permissions in the path.
+
+    $ mina setup
+    -----> Setting up
+           $ mkdir -p /var/www/kickstack.me
+           $ chmod g+r,a+rwx /var/www/kickstack.me
+           $ mkdir -p /var/www/kickstack.me/releases
+           $ mkdir -p /var/www/kickstack.me/shared
+           ...
+
+### Task - deploy:force_unlock
+
+Removes the deploy lock file. If a deploy is terminated midway, it may leave a
+lock file to signal that deploys shouldn't be made. This forces the removal of
+that lock file.
+
+    $ mina deploy
+    -----> ERROR: another deployment is ongoing.
+           Delete the lock file to continue.
+
+    $ mina deploy:force_unlock
+    -----> Unlocking
+           $ rm /var/www/kickstack.me/deploy.lock
+
+    $ mina deploy
+    # The deploy should proceed now
+
+Addons: Git
+-----------
+
+To deploy projects using git, add this to your `deploy.rb`:
+
+``` ruby
+require 'mina/git'
+
+set :repository, 'https://github.com/you/your-app.git'
+```
+
+### Settings
+
+This introduces the following settings:
+
+* `repository` - The repository path to clone from. *Required.*
+
+* `revision` - The SHA1 of the commit to be deployed. Defaults to whatever is
+the current HEAD in your local copy.
+
+### Task - git:clone
+
+Clones from the repo into the current folder.
+
+Addons: Bundler
+---------------
+
+To manage Bundler installations, add this to your `deploy.rb`:
+
+``` ruby
+require 'mina/bundler'
+```
+
+### Settings
+
+This introduces the following settings:
+
+* `bundle_path` - The path where bundles are going to be installed. Defaults to
+`./vendor/bundler`.
+
+* `bundle_options` - Options that will be passed onto `bundle install`.  
+  Defaults to
+`--without development:test --path "#{bundle_path}" --binstubs bin/
+--deployment"`.
+
+### Task - bundle:install
+
+Invokes `bundle:install` on the current directory, creating the bundle
+path (specified in `bundle_path`), and invoking `bundle install`.
+
+The `bundle_path` is only created if `bundle_path` is set (which is on
+by default).
+
+Addons: Rails
+-------------
+
+To manage Rails project installations, add this to your `deploy.rb`:
+
+``` ruby
+require 'mina/rails'
+```
+
+### Settings
+
+This introduces the following settings. All of them are optional.
+
+ * `bundle_prefix` - Prefix to run commands via Bundler. Defaults to
+ `RAILS_ENV="#{rails_env}" bundle exec`.
+
+ * `rake` - The `rake` command. Defaults to `#{bundle_prefix} rake`.
+
+ * `rails` - The `rails` command. Defaults to `#{bundle_prefix} rails`.
+
+ * `rails_env` - The environment to run rake commands in. Defaults to
+ `production`.
+
+### Task - rails:db_migrate
+
+Invokes rake to migrate the database using `rake db:migrate`.
+
+### Task - rails:assets_precompile
+
+Precompiles assets. This invokes `rake assets:precomplie`.
+
+It also checks the current version to see if it has assets compiled. If it does,
+it reuses them, skipping the compilation step. To stop this behavior, invoke
+the `mina` command with `force_assets=1`.
+
+### Task - rails:assets_precompile:force
+
+Precompiles assets. This always skips the "reuse old assets if possible" step.
+
+Development & testing
+---------------------
+
+To test out stuff in development:
+
+    # Run specs
+    $ rspec
+    $ rspec -t ssh     # Run SSH tests (read test_env/config/deploy.rb first)
+    $ rake=0.9 rspec
+    $ rake=0.8 rspec
+
+    # Alias your 'mina' to use it everywhere
+    $ alias mina="`pwd -LP`/bin/mina"
+
+### Doing test deploys
+
+Try out the test environment:
+
+    $ cd test_env
+    $ mina deploy --simulate
+    $ mina deploy
+
+    # There's an rspec task for it too
+    $ rspec -t ssh
+
+### Gem management
+
+    # To release the gem:
+    # Install the Git changelog helper: https://gist.github.com/2880525
+    $ vim lib/mina/version.rb
+    $ git clog -w
+    $ vim HISTORY.md
+    $ rake release
+
+    $ rake build      # Builds the gem file
+    $ rake install    # Installs the gem locally
+
+Issues
+------
+
+File issues at the [issue tracker][issues] (github.com). You may also look at
+the [Trello board][trello] (trello.com) we use for development.
+
+Acknowledgements
+----------------
+
+© 2012, Nadarei. Released under the [MIT 
+License](http://www.opensource.org/licenses/mit-license.php).
+
+Mina is authored and maintained by [Rico Sta. Cruz][rsc] and [Michael 
+Galero][mg] with help from its [contributors][c]. It is sponsored by our 
+startup, [Nadarei][nd].
+
+ * [Nadarei](http://nadarei.co) (nadarei.co)
+ * [Github](http://github.com/nadarei) (@nadarei)
+
+Rico:
+
+ * [My website](http://ricostacruz.com) (ricostacruz.com)
+ * [Github](http://github.com/rstacruz) (@rstacruz)
+ * [Twitter](http://twitter.com/rstacruz) (@rstacruz)
+
+Michael:
+
+ * [My website][mg] (michaelgalero.com)
+ * [Github](http://github.com/mikong) (@mikong)
+
+[rsc]: http://ricostacruz.com
+[mg]:  http://devblog.michaelgalero.com/
+[c]:   http://github.com/nadarei/mina/contributors
+[nd]:  http://nadarei.co
+[issues]: https://github.com/nadarei/mina/issues
+[trello]: https://trello.com/board/mina/4fc8b3023d9c9a4d72e573e6