g5_sibling_deployer_engine 0.2.6 → 0.3.2

checksums.yaml

@@ -1,15 +1,7 @@
 ---
-!binary "U0hBMQ==":
-  metadata.gz: !binary |-
-    NGZlNTEwM2NlNTRkOGYwMjA3MWJiMDAwNzg2MTEzYzA0ZTRmMjBlZQ==
-  data.tar.gz: !binary |-
-    MzkyY2IxYThmMjJhNGU4YjAyMDAxNjU0N2Q5YmNkMWEwNTU2ZWJkNg==
-!binary "U0hBNTEy":
-  metadata.gz: !binary |-
-    NWY5NDE0ZDYyZDQzMzFhNGE3ZWRmY2JlNWRiYmM2MzMwZDFiMzUyMWQ1MDYz
-    YTJjZWEyMDY2NjExOTBjMDhmODg0NjUxYjQ5ZWVlZjQxZTk0ZDg3YjJlNjZi
-    MjZjNTU0NDhlYjRlMzkyY2M4ZjQ1NzAyZmYzMDQxN2RiZmMzNWU=
-  data.tar.gz: !binary |-
-    NjUyMGIzODAyYjA3OWY5MjA1MDFhY2E3YmUyMjY5NDAyZTdkYWJmNjFhNzFi
-    NzIzNWNlOTIyMjE3MDg2M2MwMDVlMjYxNDI5YjhjNzc2M2FiMmNmOGY4ODgz
-    Njc2NDMwYzY2MjVlZTM3MWJlZjA4NTYzNjZlYWUxYzhlYTI2NDU=
+SHA1:
+  metadata.gz: d83ad1287ed9ff50ce0cc2172afff1f7f238d9dc
+  data.tar.gz: 2dd66c03e5aa0e98cce199e9fec434396436b7e4
+SHA512:
+  metadata.gz: 85726997938a708c8d7638fdfc29cbe3632dee50237d57cfacc63cb54ed7c1ec79d5816e309b17ed33197af7245cfb0de9a856966f35b6567f6d4d44afe49633
+  data.tar.gz: 7b781499db83a5c5525addcb9d3a6a5c24bb3711a2dc749739dabff72b3fd385b5edf80ac1097f003716de4cedf473f1cec479f75dc05d027a0c8a87df2f1843

data/.gitignore

@@ -1,19 +1,10 @@
-*.gem
-*.rbc
-.bundle
-.config
-.yardoc
 Gemfile.lock
-InstalledFiles
-_yardoc
-coverage
-doc/
-lib/bundler/man
-pkg
-rdoc
-spec/reports
-test/tmp
-test/version_tmp
-tmp
-
-spec/dummy/log/*
+.bundle/
+log/*.log
+pkg/
+spec/dummy/db/*.sqlite3
+spec/dummy/db/*.sqlite3-journal
+spec/dummy/log/*.log
+spec/dummy/tmp/
+spec/dummy/.sass-cache
+coverage/

data/.travis.yml

@@ -1,8 +1,7 @@
 language: ruby
 rvm:
-  - 1.9.3
-script:
-  - bundle exec rspec
+  - 2.1.1
+script: bundle exec rspec
 notifications:
   campfire:
     rooms:

data/Gemfile

@@ -1,6 +1,16 @@
-source 'https://rubygems.org'
+source "https://rubygems.org"
 
-# Specify your gem's dependencies in g5_sibiling_deployer_engine.gemspec
+# Declare your gem's dependencies in g5_sibling_deployer_engine.gemspec.
+# Bundler will treat runtime dependencies like base dependencies, and
+# development dependencies will be added by default to the :development group.
 gemspec
 
+# Declare any dependencies that are still in development here instead of in
+# your gemspec. These might include edge Rails or gems from your path or
+# Git. Remember to move these dependencies to your gemspec before releasing
+# your gem to rubygems.org.
+
+# To use debugger
+# gem 'debugger'
+
 gem "codeclimate-test-reporter", group: :test, require: nil

data/README.md

@@ -8,13 +8,12 @@ Provides models, views, controllers, routes, and rake tasks for deploying Siblin
 
 ## Current Version
 
-0.2.6
+0.3.2
 
 
 ## Requirements
 
 * ["rails"](http://rubygems.org/gems/rails)
-* ["table_cloth"](http://rubygems.org/gems/table_cloth)
 * ["state_machine"](http://rubygems.org/gems/state_machine)
 * ["heroku_resque_autoscaler"](http://rubygems.org/gems/heroku_resque_autoscaler)
 * ["github_heroku_deployer"](http://rubygems.org/gems/github_heroku_deployer)

data/Rakefile

@@ -1,2 +1,32 @@
-#!/usr/bin/env rake
-require "bundler/gem_tasks"
+begin
+  require 'bundler/setup'
+rescue LoadError
+  puts 'You must `gem install bundler` and `bundle install` to run rake tasks'
+end
+
+require 'rdoc/task'
+
+RDoc::Task.new(:rdoc) do |rdoc|
+  rdoc.rdoc_dir = 'rdoc'
+  rdoc.title    = 'G5SiblingDeployerEngine'
+  rdoc.options << '--line-numbers'
+  rdoc.rdoc_files.include('README.rdoc')
+  rdoc.rdoc_files.include('lib/**/*.rb')
+end
+
+
+
+
+Bundler::GemHelper.install_tasks
+
+require 'rake/testtask'
+
+Rake::TestTask.new(:test) do |t|
+  t.libs << 'lib'
+  t.libs << 'test'
+  t.pattern = 'test/**/*_test.rb'
+  t.verbose = false
+end
+
+
+task default: :test

data/app/models/sibling/deploy.rb

@@ -1,6 +1,4 @@
 class Sibling::Deploy < ActiveRecord::Base
-  attr_accessible :sibling_id, :instruction_id, :manual, :state
-  attr_accessible :git_repo, :heroku_repo, :heroku_app_name
 
   belongs_to :sibling
   belongs_to :instruction
@@ -28,8 +26,8 @@ class Sibling::Deploy < ActiveRecord::Base
     end
   end
 
-  scope :manual, where(manual: true)
-  scope :automatic, where(manual: false)
+  scope :manual, -> { where(manual: true) }
+  scope :automatic, -> { where(manual: false) }
 
   def deploy
     start!

data/app/models/sibling/instruction.rb

@@ -2,8 +2,6 @@ require 'open-uri'
 
 class Sibling::Instruction < ActiveRecord::Base
 
-  attr_accessible :uid, :name, :published_at
-
   has_many :deploys
   has_many :siblings, through: :deploys
 
@@ -44,7 +42,7 @@ class Sibling::Instruction < ActiveRecord::Base
     end
 
     def find_or_create_from_hentry(hentry)
-      find_or_create_by_uid(hentry.uid.to_s) do |instruction|
+      find_or_create_by(uid: hentry.uid.to_s) do |instruction|
         hcard = instruction(hentry)
         instruction.name = hcard.name.to_s
         instruction.published_at = hentry.updated.value

data/app/models/sibling.rb

@@ -1,6 +1,4 @@
 class Sibling < ActiveRecord::Base
-  attr_accessible :uid, :name, :git_repo, :heroku_repo, :heroku_app_name
-
   has_many :deploys
   has_many :instructions, through: :deploys
 
@@ -31,7 +29,7 @@ class Sibling < ActiveRecord::Base
     end
 
     def find_or_create_from_hcard(hcard)
-      find_or_create_by_uid(hcard.uid.to_s) do |sibling|
+      find_or_create_by(uid: hcard.uid.to_s) do |sibling|
         sibling.name = hcard.name.to_s
         sibling.git_repo = hcard.g5_git_repo.to_s
         sibling.heroku_repo = hcard.g5_heroku_repo.to_s

data/app/views/siblings/deploys/index.html.erb

@@ -2,14 +2,33 @@
 
 <%= render partial: "siblings/nav", locals: { page: :deploys } %>
 
-<%= simple_table_for @siblings_deploys do |t| %>
-  <% t.column :id %>
-  <% t.column :created_at %>
-  <% t.column :heroku_app_name %>
-  <% t.column :state %>
-  <% t.column :git_repo %>
-  <% t.column :heroku_repo %>
-  <% t.column :sibling_id %>
-  <% t.column :instruction_id %>
-  <% t.column :manual %>
-<% end %>
+<table class="table table-striped">
+  <thead>
+    <tr>
+      <td>Id</td>
+      <td>Created at</td>
+      <td>Heroku app name</td>
+      <td>State</td>
+      <td>Git repo</td>
+      <td>Heroku Repo</td>
+      <td>Sibling id</td>
+      <td>Instruction id</td>
+      <td>Manual</td>
+    </tr>
+  </thead>
+  <tbody>
+    <% @siblings_deploys.each do |t| %>
+      <tr>
+        <td>t.id</td>
+        <td>t.created_at</td>
+        <td>t.heroku_app_name</td>
+        <td>t.state</td>
+        <td>t.git_repo</td>
+        <td>t.heroku_repo</td>
+        <td>t.sibling_id</td>
+        <td>t.instruction_id</td>
+        <td>t.manual</td>
+      </tr>
+    <% end %>
+  </tbody>
+</table>

data/app/views/siblings/index.html.erb

@@ -2,15 +2,32 @@
 
 <%= render partial: "nav", locals: { page: :siblings } %>
 
-<%= simple_table_for @siblings do |t| %>
-  <% t.column :id %>
-  <% t.column :name %>
-  <% t.column :heroku_app_name %>
-  <% t.column :git_repo %>
-  <% t.column :heroku_repo %>
-  <% t.actions do %>
-    <% action { |sibling| link_to "UID", sibling.uid, class: "btn" } %>
-    <% action { |sibling| sibling.main_app? ? "" :
-        link_to("Deploy", deploy_sibling_path(sibling), class: "btn", method: :post) } %>
-  <% end %>
-<% end %>
+<table class="table table-striped">
+  <thead>
+    <tr>
+      <td>Id</td>
+      <td>Name</td>
+      <td>Heroku app name</td>
+      <td>Git repo</td>
+      <td>Heroku repo</td>
+      <td>Actions</td>
+    </tr>
+  </thead>
+  <tbody>
+    <% @siblings.each do |t| %>
+      <tr>
+        <td>t.id</td>
+        <td>t.name</td>
+        <td>t.heroku_app_name</td>
+        <td>t.git_repo</td>
+        <td>t.heroku_repo</td>
+        <td>
+          <%= link_to 'UID', t.uid, class: "btn" %>
+          <% unless t.main_app? %>
+            <%= link_to "Deploy", deploy_sibling_path(t), class: "btn", method: post %>
+          <% end %>
+        </td>
+      </tr>
+    <% end %>
+  </tbody>
+</table>

data/app/views/siblings/instructions/index.html.erb

@@ -2,12 +2,27 @@
 
 <%= render partial: "siblings/nav", locals: { page: :instructions } %>
 
-<%= simple_table_for @siblings_instructions do |t| %>
-  <% t.column :id %>
-  <% t.column :name %>
-  <% t.column :published_at %>
-  <% t.column :created_at %>
-  <% t.actions do %>
-    <% action { |instruction| link_to "UID", instruction.uid, class: "btn" } %>
-  <% end %>
-<% end %>
+<table class="table table-striped">
+  <thead>
+    <tr>
+      <td>Id</td>
+      <td>Name</td>
+      <td>Published at</td>
+      <td>Created at</td>
+      <td>Actions</td>
+    </tr>
+  </thead>
+  <tbody>
+    <% @siblings_instructions.each do |t| %>
+      <tr>
+        <td>t.id</td>
+        <td>t.name</td>
+        <td>t.published_at</td>
+        <td>t.created_at</td>
+        <td>
+          <%= link_to 'UID', t.uid, class: "btn" %>
+        </td>
+      </tr>
+    <% end %>
+  </tbody>
+</table>

data/g5_sibling_deployer_engine.gemspec

@@ -18,17 +18,16 @@ Gem::Specification.new do |gem|
   gem.test_files    = gem.files.grep(%r{^(test|spec|features)/})
   gem.require_paths = ["lib"]
 
-  gem.add_dependency "rails", "~> 3.2.12"
-  gem.add_dependency "table_cloth", "~> 0.2.1"
-  gem.add_dependency "state_machine", "~> 1.1.2"
+  gem.add_dependency "rails", "~> 4.0.3"
+  gem.add_dependency "state_machine", "~> 1.2.0"
   gem.add_dependency "heroku_resque_autoscaler", "~> 0.1.0"
   gem.add_dependency "microformats2", "~> 2.0.0"
   gem.add_dependency "github_heroku_deployer", "~> 0.2.0"
 
   gem.add_development_dependency "sqlite3", "~> 1.3.6"
-  gem.add_development_dependency "simplecov", "~> 0.7.1"
-  gem.add_development_dependency "rspec-rails", "~> 2.12.0"
-  gem.add_development_dependency "guard-rspec", "~> 2.1.0"
+  gem.add_development_dependency "simplecov", "~> 0.8.2"
+  gem.add_development_dependency "rspec-rails", "~> 2.14.1"
+  gem.add_development_dependency "guard-rspec", "~> 4.2.8"
   gem.add_development_dependency "spork", "~> 0.9.2"
   gem.add_development_dependency "rb-fsevent", "~> 0.9.2"
 end

data/lib/g5_sibling_deployer_engine/version.rb

@@ -1,3 +1,3 @@
 module G5SiblingDeployerEngine
-  VERSION = "0.2.6"
+  VERSION = "0.3.2"
 end

data/lib/g5_sibling_deployer_engine.rb

@@ -1,5 +1,4 @@
 require "rails"
-require "table_cloth"
 require "state_machine"
 require "microformats2"
 require "github_heroku_deployer"

data/spec/dummy/README.rdoc

@@ -1,261 +1,28 @@
-== Welcome to Rails
+== README
 
-Rails is a web-application framework that includes everything needed to create
-database-backed web applications according to the Model-View-Control pattern.
+This README would normally document whatever steps are necessary to get the
+application up and running.
 
-This pattern splits the view (also called the presentation) into "dumb"
-templates that are primarily responsible for inserting pre-built data in between
-HTML tags. The model contains the "smart" domain objects (such as Account,
-Product, Person, Post) that holds all the business logic and knows how to
-persist themselves to a database. The controller handles the incoming requests
-(such as Save New Account, Update Product, Show Post) by manipulating the model
-and directing data to the view.
+Things you may want to cover:
 
-In Rails, the model is handled by what's called an object-relational mapping
-layer entitled Active Record. This layer allows you to present the data from
-database rows as objects and embellish these data objects with business logic
-methods. You can read more about Active Record in
-link:files/vendor/rails/activerecord/README.html.
+* Ruby version
 
-The controller and view are handled by the Action Pack, which handles both
-layers by its two parts: Action View and Action Controller. These two layers
-are bundled in a single package due to their heavy interdependence. This is
-unlike the relationship between the Active Record and Action Pack that is much
-more separate. Each of these packages can be used independently outside of
-Rails. You can read more about Action Pack in
-link:files/vendor/rails/actionpack/README.html.
+* System dependencies
 
+* Configuration
 
-== Getting Started
+* Database creation
 
-1. At the command prompt, create a new Rails application:
-       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+* Database initialization
 
-2. Change directory to <tt>myapp</tt> and start the web server:
-       <tt>cd myapp; rails server</tt> (run with --help for options)
+* How to run the test suite
 
-3. Go to http://localhost:3000/ and you'll see:
-       "Welcome aboard: You're riding Ruby on Rails!"
+* Services (job queues, cache servers, search engines, etc.)
 
-4. Follow the guidelines to start developing your application. You can find
-the following resources handy:
+* Deployment instructions
 
-* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
-* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+* ...
 
 
-== Debugging Rails
-
-Sometimes your application goes wrong. Fortunately there are a lot of tools that
-will help you debug it and get it back on the rails.
-
-First area to check is the application log files. Have "tail -f" commands
-running on the server.log and development.log. Rails will automatically display
-debugging and runtime information to these files. Debugging info will also be
-shown in the browser on requests from 127.0.0.1.
-
-You can also log your own messages directly into the log file from your code
-using the Ruby logger class from inside your controllers. Example:
-
-  class WeblogController < ActionController::Base
-    def destroy
-      @weblog = Weblog.find(params[:id])
-      @weblog.destroy
-      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
-    end
-  end
-
-The result will be a message in your log file along the lines of:
-
-  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
-
-More information on how to use the logger is at http://www.ruby-doc.org/core/
-
-Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
-several books available online as well:
-
-* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
-* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
-
-These two books will bring you up to speed on the Ruby language and also on
-programming in general.
-
-
-== Debugger
-
-Debugger support is available through the debugger command when you start your
-Mongrel or WEBrick server with --debugger. This means that you can break out of
-execution at any point in the code, investigate and change the model, and then,
-resume execution! You need to install ruby-debug to run the server in debugging
-mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
-
-  class WeblogController < ActionController::Base
-    def index
-      @posts = Post.all
-      debugger
-    end
-  end
-
-So the controller will accept the action, run the first line, then present you
-with a IRB prompt in the server window. Here you can do things like:
-
-  >> @posts.inspect
-  => "[#<Post:0x14a6be8
-          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
-       #<Post:0x14a6620
-          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
-  >> @posts.first.title = "hello from a debugger"
-  => "hello from a debugger"
-
-...and even better, you can examine how your runtime objects actually work:
-
-  >> f = @posts.first
-  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
-  >> f.
-  Display all 152 possibilities? (y or n)
-
-Finally, when you're ready to resume execution, you can enter "cont".
-
-
-== Console
-
-The console is a Ruby shell, which allows you to interact with your
-application's domain model. Here you'll have all parts of the application
-configured, just like it is when the application is running. You can inspect
-domain models, change values, and save to the database. Starting the script
-without arguments will launch it in the development environment.
-
-To start the console, run <tt>rails console</tt> from the application
-directory.
-
-Options:
-
-* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
-  made to the database.
-* Passing an environment name as an argument will load the corresponding
-  environment. Example: <tt>rails console production</tt>.
-
-To reload your controllers and models after launching the console run
-<tt>reload!</tt>
-
-More information about irb can be found at:
-link:http://www.rubycentral.org/pickaxe/irb.html
-
-
-== dbconsole
-
-You can go to the command line of your database directly through <tt>rails
-dbconsole</tt>. You would be connected to the database with the credentials
-defined in database.yml. Starting the script without arguments will connect you
-to the development database. Passing an argument will connect you to a different
-database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
-PostgreSQL and SQLite 3.
-
-== Description of Contents
-
-The default directory structure of a generated Ruby on Rails application:
-
-  |-- app
-  |   |-- assets
-  |       |-- images
-  |       |-- javascripts
-  |       `-- stylesheets
-  |   |-- controllers
-  |   |-- helpers
-  |   |-- mailers
-  |   |-- models
-  |   `-- views
-  |       `-- layouts
-  |-- config
-  |   |-- environments
-  |   |-- initializers
-  |   `-- locales
-  |-- db
-  |-- doc
-  |-- lib
-  |   `-- tasks
-  |-- log
-  |-- public
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   |-- cache
-  |   |-- pids
-  |   |-- sessions
-  |   `-- sockets
-  `-- vendor
-      |-- assets
-          `-- stylesheets
-      `-- plugins
-
-app
-  Holds all the code that's specific to this particular application.
-
-app/assets
-  Contains subdirectories for images, stylesheets, and JavaScript files.
-
-app/controllers
-  Holds controllers that should be named like weblogs_controller.rb for
-  automated URL mapping. All controllers should descend from
-  ApplicationController which itself descends from ActionController::Base.
-
-app/models
-  Holds models that should be named like post.rb. Models descend from
-  ActiveRecord::Base by default.
-
-app/views
-  Holds the template files for the view that should be named like
-  weblogs/index.html.erb for the WeblogsController#index action. All views use
-  eRuby syntax by default.
-
-app/views/layouts
-  Holds the template files for layouts to be used with views. This models the
-  common header/footer method of wrapping views. In your views, define a layout
-  using the <tt>layout :default</tt> and create a file named default.html.erb.
-  Inside default.html.erb, call <% yield %> to render the view using this
-  layout.
-
-app/helpers
-  Holds view helpers that should be named like weblogs_helper.rb. These are
-  generated for you automatically when using generators for controllers.
-  Helpers can be used to wrap functionality for your views into methods.
-
-config
-  Configuration files for the Rails environment, the routing map, the database,
-  and other dependencies.
-
-db
-  Contains the database schema in schema.rb. db/migrate contains all the
-  sequence of Migrations for your schema.
-
-doc
-  This directory is where your application documentation will be stored when
-  generated using <tt>rake doc:app</tt>
-
-lib
-  Application specific libraries. Basically, any kind of custom code that
-  doesn't belong under controllers, models, or helpers. This directory is in
-  the load path.
-
-public
-  The directory available for the web server. Also contains the dispatchers and the
-  default HTML files. This should be set as the DOCUMENT_ROOT of your web
-  server.
-
-script
-  Helper scripts for automation and generation.
-
-test
-  Unit and functional tests along with fixtures. When using the rails generate
-  command, template test files will be generated for you and placed in this
-  directory.
-
-vendor
-  External libraries that the application depends on. Also includes the plugins
-  subdirectory. If the app has frozen rails, those gems also go here, under
-  vendor/rails/. This directory is in the load path.
+Please feel free to use a different markup language if you do not plan to run
+<tt>rake doc:app</tt>.