Permalink
Browse files

initial commit

  • Loading branch information...
0 parents commit 4a93bf51f8b67f15d54bb5736bd1854566a0df4a @bsodmike committed Oct 1, 2011
Showing with 1,544 additions and 0 deletions.
  1. +6 −0 .gitignore
  2. +1 −0 .rspec
  3. +1 −0 .rvmrc
  4. +48 −0 Gemfile
  5. +35 −0 Guardfile
  6. +261 −0 README
  7. +33 −0 README.md
  8. +7 −0 Rakefile
  9. BIN app/assets/images/rails.png
  10. +9 −0 app/assets/javascripts/application.js
  11. +7 −0 app/assets/stylesheets/application.css
  12. +3 −0 app/controllers/application_controller.rb
  13. +6 −0 app/controllers/public_controller.rb
  14. +2 −0 app/helpers/application_helper.rb
  15. 0 app/mailers/.gitkeep
  16. 0 app/models/.gitkeep
  17. +32 −0 app/views/layouts/application.html.erb
  18. +2 −0 app/views/public/index.html.erb
  19. +4 −0 config.ru
  20. +54 −0 config/application.rb
  21. +6 −0 config/boot.rb
  22. +8 −0 config/cucumber.yml
  23. +28 −0 config/database.yml
  24. +5 −0 config/environment.rb
  25. +30 −0 config/environments/development.rb
  26. +60 −0 config/environments/production.rb
  27. +42 −0 config/environments/test.rb
  28. +7 −0 config/initializers/backtrace_silencers.rb
  29. +10 −0 config/initializers/inflections.rb
  30. +5 −0 config/initializers/mime_types.rb
  31. +7 −0 config/initializers/secret_token.rb
  32. +8 −0 config/initializers/session_store.rb
  33. +14 −0 config/initializers/wrap_parameters.rb
  34. +5 −0 config/locales/en.yml
  35. +6 −0 config/routes.rb
  36. +7 −0 db/seeds.rb
  37. +2 −0 doc/README_FOR_APP
  38. +254 −0 features/step_definitions/web_steps.rb
  39. +23 −0 features/support/env.rb
  40. +33 −0 features/support/paths.rb
  41. +39 −0 features/support/selectors.rb
  42. 0 lib/assets/.gitkeep
  43. 0 lib/tasks/.gitkeep
  44. +65 −0 lib/tasks/cucumber.rake
  45. 0 log/.gitkeep
  46. +26 −0 public/404.html
  47. +26 −0 public/422.html
  48. +26 −0 public/500.html
  49. 0 public/favicon.ico
  50. +241 −0 public/index.html.disable
  51. +5 −0 public/robots.txt
  52. +10 −0 script/cucumber
  53. +6 −0 script/rails
  54. +29 −0 spec/spec_helper.rb
  55. 0 vendor/assets/stylesheets/.gitkeep
  56. 0 vendor/plugins/.gitkeep
@@ -0,0 +1,6 @@
+Gemfile.lock
+.bundle
+db/*.sqlite3
+log/*.log
+tmp/
+.sass-cache/
1 .rspec
@@ -0,0 +1 @@
+--colour
1 .rvmrc
@@ -0,0 +1 @@
+rvm use 1.9.2@rails31 --create
48 Gemfile
@@ -0,0 +1,48 @@
+source 'http://rubygems.org'
+
+gem 'rails', '3.1.0'
+
+# Gems used only for assets and not required
+# in production environments by default.
+group :assets do
+ gem 'sass-rails', " ~> 3.1.0"
+ gem 'coffee-rails', "~> 3.1.0"
+ gem 'uglifier'
+end
+
+gem 'jquery-rails'
+gem 'cancan'
+gem 'devise'
+gem 'vidibus-routing_error'
+gem 'kaminari'
+gem 'rspec-rails', :group => [:development, :test]
+gem 'pry', :group => [:development, :test]
+
+group :production do
+ gem 'mysql2', '< 0.3'
+end
+
+group :development do
+ # do bundle install --without production
+ gem 'delorean'
+ gem 'thin'
+ gem 'sqlite3'
+ gem 'hirb-unicode'
+ gem 'ruby-debug', :platform => :ruby_18
+ gem 'ruby-debug19', :platform => :ruby_19
+ gem 'rails-erd'
+ gem 'yard'
+end
+
+group :test do
+ gem 'factory_girl_rails'
+ gem 'capybara'
+ gem 'cucumber-rails'
+ gem 'guard-rspec'
+ gem 'guard-cucumber'
+ gem 'database_cleaner'
+ gem 'rb-fsevent'
+ gem "spork", "> 0.9.0.rc"
+ gem "guard-spork"
+ gem 'guard', :git => 'git://github.com/guard/guard.git'
+end
@@ -0,0 +1,35 @@
+# A sample Guardfile
+# More info at https://github.com/guard/guard#readme
+
+guard 'spork', :cucumber_env => { 'RAILS_ENV' => 'test' }, :rspec_env => { 'RAILS_ENV' => 'test' } do
+ watch('config/application.rb')
+ watch('config/environment.rb')
+ watch(%r{^config/environments/.+\.rb$})
+ watch(%r{^config/initializers/.+\.rb$})
+ watch('spec/spec_helper.rb')
+ watch(%r{^spec/support/.+\.rb$})
+end
+
+guard 'rspec', :version => 2, :cli => "-f d --drb", :all_on_start => false, :all_after_pass => false do
+ watch(%r{^spec/.+_spec\.rb$})
+ watch(%r{^lib/(.+)\.rb$}) { |m| "spec/lib/#{m[1]}_spec.rb" }
+ watch('spec/spec_helper.rb') { "spec" }
+
+ # Rails example
+ watch(%r{^spec/.+_spec\.rb$})
+ watch(%r{^app/(.+)\.rb$}) { |m| "spec/#{m[1]}_spec.rb" }
+ watch(%r{^lib/(.+)\.rb$}) { |m| "spec/lib/#{m[1]}_spec.rb" }
+ watch(%r{^app/controllers/(.+)_(controller)\.rb$}) { |m| ["spec/routing/#{m[1]}_routing_spec.rb", "spec/#{m[2]}s/#{m[1]}_#{m[2]}_spec.rb", "spec/acceptance/#{m[1]}_spec.rb"] }
+ watch(%r{^spec/support/(.+)\.rb$}) { "spec" }
+ watch('spec/spec_helper.rb') { "spec" }
+ watch('config/routes.rb') { "spec/routing" }
+ watch('app/controllers/application_controller.rb') { "spec/controllers" }
+ # Capybara request specs
+ watch(%r{^app/views/(.+)/.*\.(erb|haml)$}) { |m| "spec/requests/#{m[1]}_spec.rb" }
+end
+
+guard 'cucumber', :cli => '--drb --no-profile --color --format progress --strict' 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
261 README
@@ -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.
@@ -0,0 +1,33 @@
+# CoreApp
+This is a Rails 3.1 app generated with pre-configured TDD/BDD stack with Guard + Spork + RSpec + Cucumber
+
+## How it was created...
+
+The following was performed on a newly generated 3.1 app:
+
+ rails new CoreApp -T --skip-bundle
+ rails g rspec:install
+ rails g cucumber:install
+ spork --bootstrap
+ guard init spork
+ guard init rspec
+ guard init cucumber
+ rails g controller Public index --helper=false --assets=false --controller-specs=false --view-specs=false
+
+## Usage
+
+Fork, clone, checkout this repo and perform the following to setup a master branch of your preference, we'll be creating it as a [new empty branch](http://book.git-scm.com/5_creating_new_empty_branches.html).
+
+ git symbolic-ref HEAD refs/heads/master
+ rm .git/index
+ git clean -fdx
+ git cherry-pick f18bf10
+ touch README
+ git add -A
+ git commit -m 'initial commit'
+ git rebase -i HEAD^
+
+The last step above will put you into interactive rebase of this commit, it's advised you rename it with a commit message of your choice.
+
+## License
+CoreApp is Copyright (c) 2010-2011 [Michael de Silva](http://www.bsodmike.com) ([@bsodmike](https://twitter.com/#!/bsodmike) &amp; [G+](https://plus.google.com/102197309611185157885/posts)), and is released under MIT-LICENSE.
Oops, something went wrong.

0 comments on commit 4a93bf5

Please sign in to comment.