blazing 0.0.16 → 0.1.0.alpha1

data/.gitignore

@@ -7,3 +7,5 @@ tags
 .idea
 coverage
 *.rbc
+results.html
+SCRATCHPAD

data/.rvmrc

@@ -4,7 +4,7 @@
 # development environment upon cd'ing into the directory
 
 # First we specify our desired <ruby>[@<gemset>], the @gemset name is optional.
-environment_id="ruby-1.9.2-p180@blazing"
+environment_id="ruby-1.9.2@blazing-rework"
 
 #
 # First we attempt to load the desired environment directly from the environment

data/Gemfile

@@ -2,13 +2,3 @@ source "http://rubygems.org"
 
 # Specify your gem's dependencies in blazing.gemspec
 gemspec
-
-gem 'rake', '0.8.7'
-gem 'rspec'
-gem 'ruby-debug19', :platforms => :ruby_19
-gem 'ruby-debug', :platforms => :ruby_18
-gem 'guard' , '0.4.0.rc'
-gem 'guard-rspec'
-gem 'growl'
-gem 'simplecov', '>= 0.4.0', :require => false, :group => :test, :platforms => :ruby_19
-gem 'rb-fsevent'

data/Gemfile.lock

@@ -1,73 +1,82 @@
 PATH
   remote: .
   specs:
-    blazing (0.0.16)
-      activesupport (>= 3.0.5)
+    blazing (0.1.0.alpha1)
+      activesupport
       grit
       i18n
-      thor (>= 0.14.6)
+      methadone
 
 GEM
   remote: http://rubygems.org/
   specs:
-    activesupport (3.0.9)
-    archive-tar-minitar (0.5.2)
-    columnize (0.3.2)
-    diff-lcs (1.1.2)
+    activesupport (3.1.1)
+      multi_json (~> 1.0)
+    aruba (0.4.6)
+      bcat (>= 0.6.1)
+      childprocess (>= 0.2.0)
+      cucumber (>= 1.0.2)
+      rdiscount (>= 1.6.8)
+      rspec (>= 2.6.0)
+    bcat (0.6.2)
+      rack (~> 1.0)
+    builder (3.0.0)
+    childprocess (0.2.2)
+      ffi (~> 1.0.6)
+    cucumber (1.1.0)
+      builder (>= 2.1.2)
+      diff-lcs (>= 1.1.2)
+      gherkin (~> 2.5.0)
+      json (>= 1.4.6)
+      term-ansicolor (>= 1.0.6)
+    diff-lcs (1.1.3)
+    ffi (1.0.9)
+    gherkin (2.5.2)
+      json (>= 1.4.6)
     grit (2.4.1)
       diff-lcs (~> 1.1)
       mime-types (~> 1.15)
     growl (1.0.3)
-    guard (0.4.0.rc)
+    guard (0.8.4)
       thor (~> 0.14.6)
-    guard-rspec (0.3.0)
-      guard (>= 0.2.2)
+    guard-cucumber (0.7.3)
+      cucumber (>= 0.10)
+      guard (>= 0.8.3)
+    guard-rspec (0.5.0)
+      guard (>= 0.8.4)
     i18n (0.6.0)
-    linecache (0.43)
-    linecache19 (0.5.12)
-      ruby_core_source (>= 0.1.4)
+    json (1.6.1)
+    methadone (0.3.0)
     mime-types (1.16)
-    rake (0.8.7)
+    multi_json (1.0.3)
+    rack (1.3.4)
+    rake (0.9.2)
     rb-fsevent (0.4.0)
-    rspec (2.5.0)
-      rspec-core (~> 2.5.0)
-      rspec-expectations (~> 2.5.0)
-      rspec-mocks (~> 2.5.0)
-    rspec-core (2.5.1)
-    rspec-expectations (2.5.0)
+    rdiscount (1.6.8)
+    rdoc (3.10)
+      json (~> 1.4)
+    rspec (2.6.0)
+      rspec-core (~> 2.6.0)
+      rspec-expectations (~> 2.6.0)
+      rspec-mocks (~> 2.6.0)
+    rspec-core (2.6.4)
+    rspec-expectations (2.6.0)
       diff-lcs (~> 1.1.2)
-    rspec-mocks (2.5.0)
-    ruby-debug (0.10.4)
-      columnize (>= 0.1)
-      ruby-debug-base (~> 0.10.4.0)
-    ruby-debug-base (0.10.4)
-      linecache (>= 0.3)
-    ruby-debug-base19 (0.11.25)
-      columnize (>= 0.3.1)
-      linecache19 (>= 0.5.11)
-      ruby_core_source (>= 0.1.4)
-    ruby-debug19 (0.11.6)
-      columnize (>= 0.3.1)
-      linecache19 (>= 0.5.11)
-      ruby-debug-base19 (>= 0.11.19)
-    ruby_core_source (0.1.5)
-      archive-tar-minitar (>= 0.5.2)
-    simplecov (0.4.2)
-      simplecov-html (~> 0.4.4)
-    simplecov-html (0.4.4)
+    rspec-mocks (2.6.0)
+    term-ansicolor (1.0.7)
     thor (0.14.6)
 
 PLATFORMS
   ruby
 
 DEPENDENCIES
+  aruba
   blazing!
   growl
-  guard (= 0.4.0.rc)
+  guard
+  guard-cucumber
   guard-rspec
-  rake (= 0.8.7)
+  rake (~> 0.9.2)
   rb-fsevent
+  rdoc
   rspec
-  ruby-debug
-  ruby-debug19
-  simplecov (>= 0.4.0)

data/Guardfile

@@ -6,4 +6,12 @@ guard 'rspec', :version => 2, :cli => "--colour --fail-fast --format nested" do
   watch(%r{^lib/(.+)\.rb})     { |m| "spec/#{m[1]}_spec.rb" }
   watch(%r{^lib/blazing/(.+)\.rb})     { |m| "spec/blazing/#{m[1]}_spec.rb" }
   watch('spec/spec_helper.rb') { "spec" }
+  watch(%r{^lib/blazing/templates/(.+)}) { "spec" }
+  watch('lib/blazing/runner.rb') { "spec/blazing/integration/*" }
+end
+
+guard 'cucumber' do
+  watch(%r{^features/.+\.feature$})
+  watch(%r{^features/support/.+$})          { 'features' }
+  watch(%r{^features/step_definitions/(.+)_steps\.rb$}) { |m| Dir[File.join("**/#{m[1]}.feature")][0] || 'features' }
 end

data/README.md

@@ -1,122 +1,46 @@
-Blazing -- Fast and painless git push deploys
-=============================================
+[![Build Status](http://travis-ci.org/effkay/blazing.png)](http://travis-ci.org/effkay/blazing)
 
-[![Build Status](http://travis-ci.org/effkay/blazing.png)](http://travis-ci.org/effkay/blazing) (but still in alpha!)
+# Blazing fast git push deploys
 
-## What
+## Overview
 
-Blazing aims to be a fast and hassle free way to deploy web
-applications. It may work for other frameworks, but it is mainly
-designed to deploy Ruby on Rails and Rack based applications, as well as
-static sites.
+## Installation
 
-Some design goals:
+## Usage
 
-  * A deploy is just a git push to another remote. All that must be done afterwards is triggered by pre and post receveie git hooks.
-  * initial setup done by ruby script, so unexerpienced users do not
-    have to fiddle with the git config files
-  * clean API for writing your own recipes, no messy rake file jungles
-  * DRY, clean and minimal configuration file
-  * blazing fast!
+## Development & Contribution
 
-## Why
+### Improving Blazing itself
 
-I initially started working on an extension to capistrano which would
-cover most of my needs and the needs we had at [Screen
-Concept](http://www.screenconcept.ch). After a short while I noticed
-that bolting more functionality on top of capistrano was just going to
-be messy (and a PTA to maintain). We were alerady using tons of own recipes and customizations,
-capistrano multistage, capistrano-ext, etc.
+### Blazing Recipes
 
-I had a look at what others were doing and after a round of trying
-around and not getting what I wanted, I started this.
+## Contribution
 
-### Inspiration & Alternatives
+## TODO
 
-I looked at [Inploy](https://github.com/dcrec1/inploy) and [Vlad](https://github.com/seattlerb/vlad) after having used [Capistrano](https://github.com/capistrano/capistrano) for several
-years. Then got inspired by defunkt's
-[blog post](https://github.com/blog/470-deployment-script-spring-cleaning) about deployment script spring cleaning. Other's doing a similar thing with git push deployments are Mislav's [git-deploy](https://github.com/mislav/git-deploy) and [pushand](https://github.com/remi/pushand.git) by remi.
+###0.1 alpha:
 
-## Installation & Setup
+* implement hook
 
-Run `blazing init` in your project's root, this will create the necessary files to use and configure blazing.
+* implement recipes
 
-## Configuration & Blazing DSL
+* checkout branch specified when deploying (i.e git push production
+  some_feature_branch should checkout some_feature_branch on prod target)
 
-The blazing config file features a DSL similar to capistrano or other
-such systems.
+* handle target as argument in runner
 
-Examples:
+* finish readme
 
-```ruby
-repository 'git@github.com:someones/repository.git'
+### Later
 
-use [:bundler, :whenever]
-use :rvm, :rvm_string => 'ree@production'
+* recipes with options
+* read origin and set it as repository automatically
+* allow to set deployed branch in config
+* handle local deployment
 
-target :stagigng, :deploy_to => 'user@hostname:/path/to/target', :default => true
-target :production, :deploy_to => 'user@somehostname:/path/to/target'
-...
-```
-
-## Deploying
-
-```bash
-blazing deploy <target_name>
-```
-
-Or, if everyting is already set up on the remote etc. you can acutally
-just do a git push to your target name.
-
-## Development 
-
-Report Issues/Questions/Feature requests on [GitHub
-Issues](http://github.com/effkay/blazing/issues)
-
-### Extending / Fixing Blazing itself
-
-Pull requests are very welcome as long as they are well tested. Please
-create a topic branch for every separate change you intend to make.
-
-### Developing Blazing Extensions
-
-**(Still work in progress and not a stable API yet)**
-
-Example:
-
-```ruby
-class SomeFunkyRecipe < Blazing::Recipe
-
-  def self.run
-    # do something
-  end
-
-end
-```
 
 ## Authors
 
-[Felipe Kaufmann](http://github.com/effkay)
-
 ## License
 
-Copyright (c) 2011 Felipe Kaufmann
-
-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.
+See the `MIT-LICENSE` file

data/Rakefile

@@ -1,9 +1,14 @@
 require 'bundler'
-Bundler::GemHelper.install_tasks
-Bundler.setup
-
+require 'rake/clean'
+require 'cucumber'
+require 'cucumber/rake/task'
+require 'rdoc/task'
 require 'rspec/core/rake_task'
 
+include Rake::DSL
+
+Bundler::GemHelper.install_tasks
+
 desc "Run specs"
 RSpec::Core::RakeTask.new do |t|
   # t.rspec_opts = %w(--colour --fail-fast --format nested)
@@ -11,4 +16,16 @@ RSpec::Core::RakeTask.new do |t|
   t.ruby_opts  = %w(-w)
 end
 
-task :default => :spec
+CUKE_RESULTS = 'results.html'
+CLEAN << CUKE_RESULTS
+Cucumber::Rake::Task.new(:features) do |t|
+  t.cucumber_opts = "features --format html -o #{CUKE_RESULTS} --format progress -x"
+  t.fork = false
+end
+
+Rake::RDocTask.new do |rd|
+  rd.main = "README.rdoc"
+  rd.rdoc_files.include("README.rdoc","lib/**/*.rb","bin/**/*")
+end
+
+task :default => [:spec,:features]

data/bin/blazing

@@ -1,11 +1,29 @@
-#!/usr/bin/env ruby
+#!/usr/bin/env ruby -w
 
 require 'bundler'
 Bundler.setup
 
-require 'thor'
-require 'thor/group'
+require 'optparse'
+require 'methadone'
 require 'blazing'
-require 'blazing/cli/base'
+require 'blazing/config'
+require 'blazing/runner'
 
-Blazing::CLI::Base.start
+include Methadone::Main
+
+main do |command, target|
+  if command == 'init'
+    config = nil
+  else
+    config = Blazing::Config.parse(options[:file])
+  end
+
+  runner = Blazing::Runner.new(config, target)
+  runner.exec(command)
+end
+
+arg :command
+arg :target, :optional
+on("-f configuration", "--file configuration", "config file location (defaults to config/blazing.rb)")
+
+go!

data/blazing.gemspec

@@ -5,24 +5,35 @@ require "blazing/version"
 Gem::Specification.new do |s|
   s.name        = "blazing"
   s.version     = Blazing::VERSION
-  s.platform    = Gem::Platform::RUBY
   s.authors     = ["Felipe Kaufmann"]
   s.email       = ["felipekaufmann@gmail.com"]
   s.homepage    = "https://github.com/effkay/blazing"
   s.summary     = %q{blazing fast deployment}
   s.description = %q{git push deployent utility, ready to be extended by your own recipes}
+
+  s.rubyforge_project = "blazing"
+
   s.files         = `git ls-files`.split("\n")
   s.test_files    = `git ls-files -- {test,spec,features}/*`.split("\n")
-  # s.executables   = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
-  s.executables   = ["blazing"]
+  s.executables   = `git ls-files -- bin/*`.split("\n").map{ |f| File.basename(f) }
   s.require_paths = ["lib"]
 
-  # TODO: better to use ~ ?
-  s.add_dependency "thor", ">= 0.14.6"
-  s.add_dependency "grit"
+  # specify any dependencies here; for example:
+  # s.add_development_dependency "rspec"
+  # s.add_runtime_dependency "rest-client"
+  s.add_development_dependency('rdoc')
+  s.add_development_dependency('aruba')
+  s.add_development_dependency('rake','~> 0.9.2')
+  s.add_development_dependency('rspec')
+  s.add_development_dependency('guard')
+  s.add_development_dependency('guard-rspec')
+  s.add_development_dependency('guard-cucumber')
+  s.add_development_dependency('growl')
+  s.add_development_dependency('rb-fsevent')
+  s.add_dependency('methadone')
+  s.add_dependency('grit')
 
   # TODO: Get rid of those, just used for guessing recipe names etc in lib/recipes.rb
-  s.add_dependency "activesupport", ">= 3.0.5"
+  s.add_dependency "activesupport"
   s.add_dependency "i18n"
-
 end

data/features/help_banner.feature

@@ -0,0 +1,13 @@
+Feature: Help Banner
+  In order to know what this gem does
+  I want to see the help banner
+
+  Scenario: Run blazing --help
+    When I get help for "blazing"
+    Then the exit status should be 0
+    And the banner should be present
+
+  Scenario:
+    When I run `blazing`
+    Then the exit status should not be 0
+    And the output should contain "'command' is required"

data/features/step_definitions/blazing_steps.rb

@@ -0,0 +1 @@
+# Put your step defintions here