crowdblog 0.0.1

data/db/migrate/20120220033923_create_vestal_versions.rb

@@ -0,0 +1,28 @@
+class CreateVestalVersions < ActiveRecord::Migration
+  def self.up
+    create_table :versions do |t|
+      t.belongs_to :versioned, :polymorphic => true
+      t.belongs_to :user, :polymorphic => true
+      t.string  :user_name
+      t.text    :modifications
+      t.integer :number
+      t.integer :reverted_from
+      t.string  :tag
+
+      t.timestamps
+    end
+
+    change_table :versions do |t|
+      t.index [:versioned_id, :versioned_type]
+      t.index [:user_id, :user_type]
+      t.index :user_name
+      t.index :number
+      t.index :tag
+      t.index :created_at
+    end
+  end
+
+  def self.down
+    drop_table :versions
+  end
+end

data/features/posts/manage_posts.feature

@@ -0,0 +1,46 @@
+@javascript
+Feature: Manage Posts
+
+  Scenario: Posts CRUD
+    Given I am signed in as "test@test.com"
+    And current user is publisher
+    And I go to the posts page
+    And I click on "New Post"
+    And I fill "A Great Post Title" as the post title
+    And I fill "Body" as the post body
+    And I press "Save"
+    Then I should see "A Great Post Title"
+    And I should see "test@test.com"
+    And the post "A Great Post Title" should be authored by current user
+    And the post "A Great Post Title" should have "a-great-post-title" as its permalink
+    When I click "Edit" for "A Great Post Title"
+    And I fill "Another Great Post Title" as the post title
+    And I press "Save"
+    Then I should see "Another Great Post Title"
+    When I click "Delete" for "Another Great Post Title"
+    Then I should not see "Another Great Post Title"
+
+  Scenario: Publish unpublish post
+    Given I am signed in as "test@test.com"
+    And current user is publisher
+    And An author with name "Johan Crupps" and email "johan@crupps.com"
+    And the following posts by "Johan Crupps":
+      | title               | body                            | published |
+      | The great gatsby    | Lorem Ipsum Cohiben Allen       | false     |
+    And I go to the posts page
+    When I click on "Publish"
+    Then the post titled "The great gatsby" is marked as published
+    And current user is set as its publisher
+    When I click on "Publish"
+    Then the post titled "The great gatsby" is marked as drafted
+
+  Scenario: Do not show posts for non-publishers
+    Given I am signed in as "test@test.com"
+    And An author with name "Johan Crupps" and email "johan@crupps.com"
+    And the following posts by "Johan Crupps":
+      | title               | body                            | published |
+      | The great gatsby    | Lorem Ipsum Cohiben Allen       | false     |
+    And I go to the posts page
+    Then I should not see "The great gatsby"
+
+

data/features/step_definitions/index_steps.rb

@@ -0,0 +1,16 @@
+Given /^the following posts by "([^"]*)":$/ do |name, table|
+  author = Crowdblog::User.find_by_name name
+  table.hashes.each_with_index do |hash, index|
+    time_index = (index * 5)
+    p = Crowdblog::Post.create!(title: hash[:title], body: hash[:body])
+    p.author = author
+    p.regenerate_permalink
+    p.save!
+    p.publish if hash[:published] == 'true'
+    p.update_attribute(:published_at, time_index.days.ago)
+  end
+end
+
+When /^I go to the index page$/ do
+  visit root_path
+end

data/features/step_definitions/interaction_steps.rb

@@ -0,0 +1,26 @@
+Given /^I click on "([^"]*)"$/ do |link_name|
+  click_link link_name
+end
+
+Given /^I press "([^"]*)"$/ do |button_name|
+  click_button button_name
+end
+
+Then /^I should see "([^"]*)"$/ do |expectation|
+  page.should have_content expectation
+end
+
+When /^I click "([^"]*)" for "([^"]*)"$/ do |link_text, row_text|
+  page.execute_script 'window.confirm = function() { return true }'
+  find("tr:contains('#{row_text}')").find("a:contains('#{link_text}')").click
+end
+
+Then /^I should not see "([^"]*)"$/ do |expectation|
+  page.should_not have_content expectation
+end
+
+Then /^I should see:$/ do |table|
+  table.raw.flatten.each do |expected|
+    page.should have_content expected
+  end
+end

data/features/step_definitions/posts_steps.rb

@@ -0,0 +1,35 @@
+Given /^I go to the posts page$/ do
+  visit posts_path
+end
+
+Given /^I fill "([^"]*)" as the post title$/ do |text|
+  fill_in 'Title', with: text
+end
+
+Given /^I fill "([^"]*)" as the post body$/ do |text|
+  fill_in 'Body', with: text
+end
+
+Then /^the post "([^"]*)" should be authored by current user$/ do |post_title|
+  post = Crowdblog::Post.find_by_title(post_title)
+  post.author.should == @current_user
+end
+
+Then /^the post "([^"]*)" should have "([^"]*)" as its permalink$/ do |post_title, permalink|
+  post = Crowdblog::Post.find_by_title(post_title)
+  post.permalink.should == permalink
+end
+
+Then /^the post titled "([^"]*)" is marked as published$/ do |post_title|
+  @current_post = Crowdblog::Post.find_by_title(post_title)
+  @current_post.should be_published
+end
+
+Then /^current user is set as its publisher$/ do
+  @current_post.publisher.should == @current_user
+end
+
+Then /^the post titled "([^"]*)" is marked as drafted$/ do |post_title|
+  @current_post = Crowdblog::Post.find_by_title(post_title)
+  @current_post.should be_drafted
+end

data/features/step_definitions/session_steps.rb

@@ -0,0 +1,15 @@
+include Devise::TestHelpers
+
+Given /^I am signed in as "([^"]*)"$/ do |email|
+  @current_user = Crowdblog::User.create!(email: email)
+  @current_user.reset_authentication_token!
+  visit crowdblog_path + "?auth_token=#{@current_user.authentication_token}"
+end
+
+Given /^An author with name "([^"]*)" and email "([^"]*)"$/ do |name, email|
+  Crowdblog::User.create!(name: name, email: email)
+end
+
+Given /^current user is publisher$/ do
+  @current_user.update_attribute(:is_publisher, true)
+end

data/features/support/env.rb

@@ -0,0 +1,69 @@
+# Added this as explained in: http://bit.ly/uJv9M7
+ENV["RAILS_ENV"] ||= "test"
+require File.expand_path("../../../spec/dummy/config/environment.rb",  __FILE__)
+ENV["RAILS_ROOT"] ||= File.dirname(__FILE__) + "../../../spec/dummy"
+
+# IMPORTANT: This file is generated by cucumber-rails - edit at your own peril.
+# It is recommended to regenerate this file in the future when you upgrade to a 
+# newer version of cucumber-rails. Consider adding your own code to a new file 
+# instead of editing this one. Cucumber will automatically load all features/**/*.rb
+# files.
+
+require 'cucumber/rails'
+
+# Capybara defaults to XPath selectors rather than Webrat's default of CSS3. In
+# order to ease the transition to Capybara we set the default here. If you'd
+# prefer to use XPath just remove this line and adjust any selectors in your
+# steps to use the XPath syntax.
+Capybara.default_selector = :css
+
+# By default, any exception happening in your Rails application will bubble up
+# to Cucumber so that your scenario will fail. This is a different from how 
+# your application behaves in the production environment, where an error page will 
+# be rendered instead.
+#
+# Sometimes we want to override this default behaviour and allow Rails to rescue
+# exceptions and display an error page (just like when the app is running in production).
+# Typical scenarios where you want to do this is when you test your error pages.
+# There are two ways to allow Rails to rescue exceptions:
+#
+# 1) Tag your scenario (or feature) with @allow-rescue
+#
+# 2) Set the value below to true. Beware that doing this globally is not
+# recommended as it will mask a lot of errors for you!
+#
+ActionController::Base.allow_rescue = false
+
+# Remove/comment out the lines below if your app doesn't have a database.
+# For some databases (like MongoDB and CouchDB) you may need to use :truncation instead.
+begin
+  DatabaseCleaner.strategy = :transaction
+rescue NameError
+  raise "You need to add database_cleaner to your Gemfile (in the :test group) if you wish to use it."
+end
+
+# You may also want to configure DatabaseCleaner to use different strategies for certain features and scenarios.
+# See the DatabaseCleaner documentation for details. Example:
+#
+#   Before('@no-txn,@selenium,@culerity,@celerity,@javascript') do
+#     # { :except => [:widgets] } may not do what you expect here
+#     # as tCucumber::Rails::Database.javascript_strategy overrides
+#     # this setting.
+#     DatabaseCleaner.strategy = :truncation
+#   end
+#
+#   Before('~@no-txn', '~@selenium', '~@culerity', '~@celerity', '~@javascript') do
+#     DatabaseCleaner.strategy = :transaction
+#   end
+#
+
+# Possible values are :truncation and :transaction
+# The :transaction strategy is faster, but might give you threading problems.
+# See https://github.com/cucumber/cucumber-rails/blob/master/features/choose_javascript_database_strategy.feature
+Cucumber::Rails::Database.javascript_strategy = :truncation
+
+# include Engine routes in Cucumber world
+module EngineRoutesHelper
+  include Crowdblog::Engine.routes.url_helpers
+end
+World(EngineRoutesHelper)

data/lib/crowdblog/engine.rb

@@ -0,0 +1,5 @@
+module Crowdblog
+  class Engine < ::Rails::Engine
+    isolate_namespace Crowdblog
+  end
+end

data/lib/crowdblog/version.rb

@@ -0,0 +1,3 @@
+module Crowdblog
+  VERSION = "0.0.1"
+end

data/lib/crowdblog.rb

@@ -0,0 +1,4 @@
+require "crowdblog/engine"
+
+module Crowdblog
+end

data/lib/tasks/crowdblog_tasks.rake

@@ -0,0 +1,4 @@
+# desc "Explaining what the task does"
+# task :crowdblog do
+#   # Task goes here
+# end

data/script/build

@@ -0,0 +1,29 @@
+#!/bin/bash
+
+# Set default variables (if not before with ENV variables)
+if [ -z $CC_RUBY ]; then CC_RUBY=1.9.2; fi
+if [ -z $CC_GEMSET ]; then CC_GEMSET=crowdblog; fi
+
+# Initialize RVM
+source "$HOME/.rvm/scripts/rvm"
+
+# Change to the gemset
+rvm $CC_RUBY@$CC_GEMSET --create --install
+
+# Is bundler installed?
+which bundle || gem install bundler
+
+echo "-- Install Gem dependencies"
+bundle install
+
+echo "-- Build project"
+export DISPLAY=:0.0
+RAILS_ENV=test rake db:migrate
+bundle exec rake
+EXIT_CODE=$?
+
+#echo "-- METRICS"
+#which metrical || gem install metrical
+#metrical > /dev/null 2>&1
+
+exit $EXIT_CODE

data/script/cucumber

@@ -0,0 +1,10 @@
+#!/usr/bin/env ruby
+
+vendored_cucumber_bin = Dir["#{File.dirname(__FILE__)}/../vendor/{gems,plugins}/cucumber*/bin/cucumber"].first
+if vendored_cucumber_bin
+  load File.expand_path(vendored_cucumber_bin)
+else
+  require 'rubygems' unless ENV['NO_RUBYGEMS']
+  require 'cucumber'
+  load Cucumber::BINARY
+end

data/script/rails

@@ -0,0 +1,8 @@
+#!/usr/bin/env ruby
+# This command will automatically be run when you run "rails" with Rails 3 gems installed from the root of your application.
+
+ENGINE_ROOT = File.expand_path('../..', __FILE__)
+ENGINE_PATH = File.expand_path('../../lib/crowdblog/engine', __FILE__)
+
+require 'rails/all'
+require 'rails/engine/commands'

data/spec/dummy/.rvmrc

@@ -0,0 +1 @@
+rvm use 1.9.3@crowdblog --create --install

data/spec/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+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.
+
+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.
+
+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.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* 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.

data/spec/dummy/Rakefile

@@ -0,0 +1,7 @@
+#!/usr/bin/env rake
+# Add your own tasks in files placed in lib/tasks ending in .rake,
+# for example lib/tasks/capistrano.rake, and they will automatically be available to Rake.
+
+require File.expand_path('../config/application', __FILE__)
+
+Dummy::Application.load_tasks

data/spec/dummy/app/assets/javascripts/application.js

@@ -0,0 +1,16 @@
+// This is a manifest file that'll be compiled into application.js, which will include all the files
+// listed below.
+//
+// Any JavaScript/Coffee file within this directory, lib/assets/javascripts, vendor/assets/javascripts,
+// or vendor/assets/javascripts of plugins, if any, can be referenced here using a relative path.
+//
+// It's not advisable to add code directly here, but if you do, it'll appear at the bottom of the
+// the compiled file.
+//
+// WARNING: THE FIRST BLANK LINE MARKS THE END OF WHAT'S TO BE PROCESSED, ANY BLANK LINE SHOULD
+// GO AFTER THE REQUIRES BELOW.
+//
+//= require jquery
+//= require jquery_ujs
+//= require_tree .
+//= require crowdblog

data/spec/dummy/app/assets/stylesheets/application.css

@@ -0,0 +1,13 @@
+/*
+ * This is a manifest file that'll be compiled into application.css, which will include all the files
+ * listed below.
+ *
+ * Any CSS and SCSS file within this directory, lib/assets/stylesheets, vendor/assets/stylesheets,
+ * or vendor/assets/stylesheets of plugins, if any, can be referenced here using a relative path.
+ *
+ * You're free to add application-wide styles to this file and they'll appear at the top of the
+ * compiled file, but it's generally better to create a new file per style scope.
+ *
+ *= require_self
+ *= require_tree .
+*/

data/spec/dummy/app/controllers/application_controller.rb

@@ -0,0 +1,3 @@
+class ApplicationController < ActionController::Base
+  protect_from_forgery
+end

data/spec/dummy/app/helpers/application_helper.rb

@@ -0,0 +1,2 @@
+module ApplicationHelper
+end

data/spec/dummy/app/views/layouts/application.html.erb

@@ -0,0 +1,14 @@
+<!DOCTYPE html>
+<html>
+<head>
+  <title>Dummy</title>
+  <%= stylesheet_link_tag    "application", :media => "all" %>
+  <%= javascript_include_tag "application" %>
+  <%= csrf_meta_tags %>
+</head>
+<body>
+
+<%= yield %>
+
+</body>
+</html>