Permalink
Browse files

adding episode 155

  • Loading branch information...
1 parent a46c8eb commit 87381b9a02baf0e224671861240d0ecaab0635ee @ryanb committed Mar 30, 2009
Showing with 8,809 additions and 0 deletions.
  1. +14 −0 episode-155/README
  2. +3 −0 episode-155/blog/.gitignore
  3. +243 −0 episode-155/blog/README
  4. +10 −0 episode-155/blog/Rakefile
  5. +10 −0 episode-155/blog/app/controllers/application_controller.rb
  6. +15 −0 episode-155/blog/app/controllers/articles_controller.rb
  7. +3 −0 episode-155/blog/app/helpers/application_helper.rb
  8. +2 −0 episode-155/blog/app/helpers/articles_helper.rb
  9. +2 −0 episode-155/blog/app/models/article.rb
  10. +6 −0 episode-155/blog/app/views/articles/index.html.erb
  11. +11 −0 episode-155/blog/app/views/articles/new.html.erb
  12. +110 −0 episode-155/blog/config/boot.rb
  13. +22 −0 episode-155/blog/config/database.yml
  14. +41 −0 episode-155/blog/config/environment.rb
  15. +17 −0 episode-155/blog/config/environments/development.rb
  16. +28 −0 episode-155/blog/config/environments/production.rb
  17. +33 −0 episode-155/blog/config/environments/test.rb
  18. +7 −0 episode-155/blog/config/initializers/backtrace_silencers.rb
  19. +10 −0 episode-155/blog/config/initializers/inflections.rb
  20. +5 −0 episode-155/blog/config/initializers/mime_types.rb
  21. +19 −0 episode-155/blog/config/initializers/new_rails_defaults.rb
  22. +15 −0 episode-155/blog/config/initializers/session_store.rb
  23. +5 −0 episode-155/blog/config/locales/en.yml
  24. +45 −0 episode-155/blog/config/routes.rb
  25. +14 −0 episode-155/blog/db/migrate/20090330052103_create_articles.rb
  26. +21 −0 episode-155/blog/db/schema.rb
  27. +2 −0 episode-155/blog/doc/README_FOR_APP
  28. +22 −0 episode-155/blog/features/manage_articles.feature
  29. +13 −0 episode-155/blog/features/step_definitions/article_steps.rb
  30. +103 −0 episode-155/blog/features/step_definitions/webrat_steps.rb
  31. +17 −0 episode-155/blog/features/support/env.rb
  32. +21 −0 episode-155/blog/features/support/paths.rb
  33. +15 −0 episode-155/blog/lib/tasks/cucumber.rake
  34. +30 −0 episode-155/blog/public/404.html
  35. +30 −0 episode-155/blog/public/422.html
  36. +30 −0 episode-155/blog/public/500.html
  37. 0 episode-155/blog/public/favicon.ico
  38. BIN episode-155/blog/public/images/rails.png
  39. +275 −0 episode-155/blog/public/index.html
  40. +2 −0 episode-155/blog/public/javascripts/application.js
  41. +963 −0 episode-155/blog/public/javascripts/controls.js
  42. +973 −0 episode-155/blog/public/javascripts/dragdrop.js
  43. +1,128 −0 episode-155/blog/public/javascripts/effects.js
  44. +4,320 −0 episode-155/blog/public/javascripts/prototype.js
  45. +5 −0 episode-155/blog/public/robots.txt
  46. +4 −0 episode-155/blog/script/about
  47. +3 −0 episode-155/blog/script/console
  48. +8 −0 episode-155/blog/script/cucumber
  49. +3 −0 episode-155/blog/script/dbconsole
  50. +3 −0 episode-155/blog/script/destroy
  51. +3 −0 episode-155/blog/script/generate
  52. +3 −0 episode-155/blog/script/performance/benchmarker
  53. +3 −0 episode-155/blog/script/performance/profiler
  54. +3 −0 episode-155/blog/script/plugin
  55. +3 −0 episode-155/blog/script/runner
  56. +3 −0 episode-155/blog/script/server
  57. +17 −0 episode-155/blog/spec/controllers/articles_controller_spec.rb
  58. +9 −0 episode-155/blog/spec/fixtures/articles.yml
  59. +11 −0 episode-155/blog/spec/helpers/articles_helper_spec.rb
  60. +14 −0 episode-155/blog/spec/models/article_spec.rb
  61. +12 −0 episode-155/blog/spec/views/articles/index.html.erb_spec.rb
  62. +9 −0 episode-155/blog/test/performance/browsing_test.rb
  63. +38 −0 episode-155/blog/test/test_helper.rb
  64. 0 episode-155/blog/vendor/.gitignore
View
@@ -0,0 +1,14 @@
+Railscasts Episode #155: Beginning with Cucumber
+
+http://railscasts.com/episodes/155
+
+Commands
+
+ rails blog
+ sudo rake gems:install RAILS_ENV=test
+ script/generate cucumber
+ cucumber features -n
+ script/generate rspec_model article title:string content:text
+ rake db:migrate
+ rake db:test:clone
+ script/generate rspec_controller articles index
@@ -0,0 +1,3 @@
+tmp/*
+log/*
+*.sqlite3
View
@@ -0,0 +1,243 @@
+== 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, start a new Rails application using the <tt>rails</tt> command
+ and your application name. Ex: rails myapp
+2. Change directory into myapp and start the web server: <tt>script/server</tt> (run with --help for options)
+3. Go to http://localhost:3000/ and get "Welcome aboard: You're riding the Rails!"
+4. Follow the guidelines to start developing your application
+
+
+== Web Servers
+
+By default, Rails will try to use Mongrel if it's are installed when started with script/server, otherwise Rails will use WEBrick, the webserver that ships with Ruby. But you can also use Rails
+with a variety of other web servers.
+
+Mongrel is a Ruby-based webserver with a C component (which requires compilation) that is
+suitable for development and deployment of Rails applications. If you have Ruby Gems installed,
+getting up and running with mongrel is as easy as: <tt>gem install mongrel</tt>.
+More info at: http://mongrel.rubyforge.org
+
+Say other Ruby web servers like Thin and Ebb or regular web servers like Apache or LiteSpeed or
+Lighttpd or IIS. The Ruby web servers are run through Rack and the latter can either be setup to use
+FCGI or proxy to a pack of Mongrels/Thin/Ebb servers.
+
+== Apache .htaccess example for FCGI/CGI
+
+# General Apache options
+AddHandler fastcgi-script .fcgi
+AddHandler cgi-script .cgi
+Options +FollowSymLinks +ExecCGI
+
+# If you don't want Rails to look in certain directories,
+# use the following rewrite rules so that Apache won't rewrite certain requests
+#
+# Example:
+# RewriteCond %{REQUEST_URI} ^/notrails.*
+# RewriteRule .* - [L]
+
+# Redirect all requests not available on the filesystem to Rails
+# By default the cgi dispatcher is used which is very slow
+#
+# For better performance replace the dispatcher with the fastcgi one
+#
+# Example:
+# RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]
+RewriteEngine On
+
+# If your Rails application is accessed via an Alias directive,
+# then you MUST also set the RewriteBase in this htaccess file.
+#
+# Example:
+# Alias /myrailsapp /path/to/myrailsapp/public
+# RewriteBase /myrailsapp
+
+RewriteRule ^$ index.html [QSA]
+RewriteRule ^([^.]+)$ $1.html [QSA]
+RewriteCond %{REQUEST_FILENAME} !-f
+RewriteRule ^(.*)$ dispatch.cgi [QSA,L]
+
+# In case Rails experiences terminal errors
+# Instead of displaying this message you can supply a file here which will be rendered instead
+#
+# Example:
+# ErrorDocument 500 /500.html
+
+ErrorDocument 500 "<h2>Application error</h2>Rails application failed to start properly"
+
+
+== 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/ including:
+
+* The Learning Ruby (Pickaxe) Book: http://www.ruby-doc.org/docs/ProgrammingRuby/
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two online (and free) 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 'gem install ruby-debug'
+Example:
+
+ class WeblogController < ActionController::Base
+ def index
+ @posts = Post.find(: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 you know!\", \"body\"=>\"Only ten..\", \"id\"=>\"2\"}>]"
+ >> @posts.first.title = "hello from a debugger"
+ => "hello from a debugger"
+
+...and even better is that 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 enter "cont"
+
+
+== Console
+
+You can interact with the domain model by starting the console through <tt>script/console</tt>.
+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.
+Passing an argument will specify a different environment, like <tt>script/console production</tt>.
+
+To reload your controllers and models after launching the console run <tt>reload!</tt>
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>script/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>script/dbconsole production</tt>.
+Currently works for mysql, postgresql and sqlite.
+
+== Description of Contents
+
+app
+ Holds all the code that's specific to this particular application.
+
+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.
+ Most models will descend from ActiveRecord::Base.
+
+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.
+
+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 script/generate 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. Contains subdirectories for images, stylesheets,
+ and javascripts. 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 script/generate scripts, 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.
View
@@ -0,0 +1,10 @@
+# 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.join(File.dirname(__FILE__), 'config', 'boot'))
+
+require 'rake'
+require 'rake/testtask'
+require 'rake/rdoctask'
+
+require 'tasks/rails'
@@ -0,0 +1,10 @@
+# Filters added to this controller apply to all controllers in the application.
+# Likewise, all the methods added will be available for all controllers.
+
+class ApplicationController < ActionController::Base
+ helper :all # include all helpers, all the time
+ protect_from_forgery # See ActionController::RequestForgeryProtection for details
+
+ # Scrub sensitive parameters from your log
+ # filter_parameter_logging :password
+end
@@ -0,0 +1,15 @@
+class ArticlesController < ApplicationController
+ def index
+ @articles = Article.all
+ end
+
+ def new
+ @article = Article.new
+ end
+
+ def create
+ @article = Article.create!(params[:article])
+ flash[:notice] = "New article created."
+ redirect_to articles_path
+ end
+end
@@ -0,0 +1,3 @@
+# Methods added to this helper will be available to all templates in the application.
+module ApplicationHelper
+end
@@ -0,0 +1,2 @@
+module ArticlesHelper
+end
@@ -0,0 +1,2 @@
+class Article < ActiveRecord::Base
+end
@@ -0,0 +1,6 @@
+<%= flash[:notice] %>
+<% for article in @articles %>
+ <p><%=h article.title %></p>
+ <p><%=h article.content %></p>
+<% end %>
+<p><%= link_to "New Article", new_article_path %></p>
@@ -0,0 +1,11 @@
+<% form_for @article do |f| %>
+ <p>
+ <%= f.label :title %><br />
+ <%= f.text_field :title %>
+ </p>
+ <p>
+ <%= f.label :content %><br />
+ <%= f.text_field :content %>
+ </p>
+ <p class="button"><%= f.submit "Create" %></p>
+<% end %>
Oops, something went wrong.

0 comments on commit 87381b9

Please sign in to comment.