adminpanel 0.1.1 → 1.0.0

data/config/routes.rb

@@ -1,16 +1,24 @@
-Adminpanel::Engine.routes.draw do
-  	resources :sections, :except => [:new]
-    resources :users
-    resources :galleries do
-    	member do 
-    		put :move_better, :as => "move_to_better"
-    		put :move_worst, :as => "move_to_worst"
-    	end
-    end
-    resources :sessions, :only => [:new, :create, :destroy]
-    resources :products
-    resources :categories
-    root :to => 'products#index'
-    match '/signout', :to => 'sessions#destroy', :via => :delete, :as => "signout"
-    match '/signin', :to => 'sessions#new', :as => "signin"
-end
+include Adminpanel::RouterHelper
+
+Adminpanel::Engine.routes.draw do
+
+    adminpanel_resources.each do |file|
+        if file
+            resources file.to_sym
+        end
+    end
+
+	resources :sections, :except => [:new, :create, :destroy]
+    match '/signout', :to => 'sessions#destroy', :via => :delete, :as => "signout"
+    match '/signin', :to => 'sessions#new', :as => "signin"
+    resources :users
+    resources :galleries do
+        member do
+            put :move_better, :as => "move_to_better"
+            put :move_worst, :as => "move_to_worst"
+        end
+    end
+    resources :sessions, :only => [:new, :create, :destroy]
+
+    root :to => 'galleries#index'
+end

data/lib/adminpanel.rb

@@ -1,7 +1,9 @@
-require "adminpanel/version"
-require "adminpanel/engine"
-
-module Adminpanel
- class AccessDenied < StandardError
- end
-end
+require "adminpanel/version"
+require "adminpanel/engine"
+require "inherited_resources"
+require "adminpanel/active_record_extension"
+require "carrierwave"
+require "carrierwave/orm/activerecord"
+
+module Adminpanel
+end

data/lib/adminpanel/active_record_extension.rb

@@ -0,0 +1,38 @@
+module ActiveRecordExtension
+  extend ActiveSupport::Concern
+  #instance methods
+  # def foo
+    
+  # end
+
+  # static(class) methods
+  module ClassMethods
+    def form_attributes
+      [{
+        "name" => {"type" => "text_field", "name" => ":name"}
+      }]
+    end
+
+    def display_name
+      "display_name"
+    end
+
+    def has_images?
+      form_attributes.each do |fields|
+      fields.each do |attribute, properties|
+        if properties["type"] == "adminpanel_file_field"
+          return true
+        end
+      end
+      end
+      return false
+    end
+
+    def icon
+      "icon-truck"
+    end
+  end
+end
+
+# include the extension 
+ActiveRecord::Base.send(:include, ActiveRecordExtension)

data/lib/adminpanel/engine.rb

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

data/lib/adminpanel/version.rb

@@ -1,3 +1,3 @@
-module Adminpanel
-  VERSION = "0.1.1"
-end
+module Adminpanel
+  VERSION = "1.0.0"
+end

data/lib/generators/adminpanel/initialize/initialize_generator.rb

@@ -0,0 +1,17 @@
+include Rails::Generators::Migration
+module Adminpanel
+	module Generators
+		class InitializeGenerator < Rails::Generators::Base
+			desc "Generate the migrations necessary to start the gem"
+    		source_root File.expand_path("../templates", __FILE__)
+
+    		def self.next_migration_number(path)
+    			Time.now.utc.strftime("%Y%m%d%H%M%S")
+    		end
+
+			def create_migrations
+        		migration_template 'create_adminpanel_tables.rb', 'db/migrate/create_adminpanel_tables.rb'
+			end
+		end
+	end
+end

data/lib/generators/adminpanel/{install/templates/migrations → initialize/templates}/create_adminpanel_tables.rb

@@ -1,65 +1,46 @@
-class CreateAdminpanelTables < ActiveRecord::Migration
-	def migrate(direction)
-		super
-		# Create a default user
-		if direction == :up
-			Adminpanel::User.new(:email => 'admin@admin.com', :name => "Admin", :password => 'password', :password_confirmation => 'password').save
-		end
-	end
-	
-	def change
-		create_table :adminpanel_products do |t|
-	      t.integer :category_id
-	      t.string :name
-	      t.string :brief
-	      t.text :description
-	      t.timestamps
-	    end
-
-	    create_table :adminpanel_users do |t|
-	      t.string :name
-	      t.string :email
-	      t.string :password_digest
-	      t.string :remember_token
-	      t.timestamps
-	    end
-	    add_index :adminpanel_users, [:email]
-	    add_index :adminpanel_users, [:remember_token]
-
-        create_table :adminpanel_galleries do |t|
-	      t.string :file
-	      t.integer :position
-	      t.timestamps
-	    end
-
-	    create_table :adminpanel_images do |t|
-	      t.string :file
-	      t.integer :foreign_key
-	      t.string :model
-	      t.timestamps
-	    end
-
-	    create_table :adminpanel_sections do |t|
-	      t.string :name
-	      t.boolean :has_description
-	      t.text :description
-	      t.string :key
-	      t.string :page
-	      t.boolean :has_image
-	      t.timestamps
-	    end
-
-	    create_table :adminpanel_clients do |t|
-	    	t.string :name
-	    	t.string :logo
-	    	t.timestamps
-	    end
-
-	    add_index :adminpanel_sections, [:key]
-
-	    create_table :adminpanel_categories do |t|
-	      t.string :name
-	      t.timestamps
-	    end
-	end
+class CreateAdminpanelTables < ActiveRecord::Migration
+	def migrate(direction)
+		super
+		# Create a default user
+		if direction == :up
+			Adminpanel::User.new(:email => 'admin@admin.com', :name => "Admin", :password => 'password', :password_confirmation => 'password').save
+		end
+	end
+	
+	def change
+	    create_table :adminpanel_users do |t|
+	      t.string :name
+	      t.string :email
+	      t.string :password_digest
+	      t.string :remember_token
+	      t.timestamps
+	    end
+	    add_index :adminpanel_users, [:email]
+	    add_index :adminpanel_users, [:remember_token]
+
+        create_table :adminpanel_galleries do |t|
+	      t.string :file
+	      t.integer :position
+	      t.timestamps
+	    end
+
+	    create_table :adminpanel_images do |t|
+	      t.string :file
+	      t.integer :foreign_key
+	      t.string :model
+	      t.timestamps
+	    end
+
+	    create_table :adminpanel_sections do |t|
+	      t.string :name
+	      t.boolean :has_description
+	      t.text :description
+	      t.string :key
+	      t.string :page
+	      t.boolean :has_image
+	      t.timestamps
+	    end
+
+	    add_index :adminpanel_sections, [:key]
+	end
 end

data/lib/generators/adminpanel/resource/resource_generator.rb

@@ -0,0 +1,105 @@
+require "action_view"
+include Rails::Generators::Migration
+module Adminpanel
+	module Generators
+		class ResourceGenerator < Rails::Generators::Base
+
+    		source_root File.expand_path("../templates", __FILE__)
+    		argument :resource_name, :type => :string, :default => "Resource"
+    		argument :fields, :type => :hash, :default => "name:string"
+			desc "Generate the resource files necessary to use a model"
+
+			def self.next_migration_number(path)
+	 			Time.now.utc.strftime("%Y%m%d%H%M%S")
+			end
+
+			def create_model
+        		template 'resource.rb', "app/models/adminpanel/#{lower_name}.rb"
+			end
+
+			def create_controller
+				template "controller.rb", "app/controllers/adminpanel/#{pluralized_name}_controller.rb"
+			end
+
+			def create_migrations
+				migration_template "migration.rb", "db/migrate/create_#{pluralized_name}_table"
+				# generate "migration.rb", "db/migrate/create_#{pluralized_name}_table"
+			end
+
+
+			private
+
+			def lower_name
+				resource_name.singularize.downcase
+			end
+
+			def capitalized_resource
+				lower_name.capitalize
+			end
+
+			def pluralized_name
+				"#{lower_name.pluralize}"
+			end
+
+			def symbolized_attributes
+		        attributes = ""
+		        fields.each do |field, type|
+		        	if type == "images"
+		            	attributes = attributes + ":images_attributes, "
+		        	else
+		            	attributes = attributes + ":#{field}, "
+		        	end
+		        end
+		        2.times do
+		        	attributes.chop! #to remove the last white space and the last ","
+		        end
+		        attributes
+			end
+
+			def adminpanel_form_attributes
+				form_hash = ""
+				fields.each do |field, type|
+					if type == "string" || type == "float"
+						form_hash = form_hash + "\n\t\t\t\t{\"#{field}\" => {\"type\" => \"text_field\", \"name\" => \"#{field}\", \"label\" => \"#{field}\", \"placeholder\" => \"#{field}\"}},"
+					elsif type == "text" || type == "wysiwyg"
+						form_hash = form_hash + "\n\t\t\t\t{\"#{field}\" => {\"type\" => \"wysiwyg_field\", \"name\" => \"#{field}\", \"label\" => \"#{field}\", \"placeholder\" => \"#{field}\"}},"
+					elsif type == "integer"
+						form_hash = form_hash + "\n\t\t\t\t{\"#{field}\" => {\"type\" => \"number_field\", \"name\" => \"#{field}\", \"label\" => \"#{field}\", \"placeholder\" => \"#{field}\"}},"
+					elsif type == "datepicker"
+						form_hash = form_hash + "\n\t\t\t\t{\"#{field}\" => {\"type\" => \"datepicker\", \"name\" => \"#{field}\", \"label\" => \"#{field}\", \"placeholder\" => \"#{field}\"}},"
+					elsif type == "images"
+						form_hash = form_hash + "\n\t\t\t\t{\"#{field}\" => {\"type\" => \"adminpanel_file_field\", \"name\" => \"#{field}\"}},"
+					end
+				end
+				form_hash
+			end
+
+			def migration_string(field, type)
+				if type == "datepicker"
+					"t.string :#{field}"
+				elsif type == "images"
+					""
+				elsif type == "wysiwyg"
+					"t.text :#{field}"
+				else
+					"t.#{type} :#{field}"
+				end
+			end
+
+			def has_images?
+				fields.each do |field, type|
+					if type == "images"
+						return true
+					end
+				end
+				return false
+			end
+
+			def image_relationship
+				return "has_many :images, :foreign_key => \"foreign_key\", :conditions => { :model => \"#{lower_name}\" }
+		accepts_nested_attributes_for :images, :allow_destroy => true
+		#remember to change the relationship if you change this model display_name"
+			end
+		end
+	end
+end

data/lib/generators/adminpanel/resource/templates/controller.rb

@@ -0,0 +1,4 @@
+module Adminpanel
+    class <%= pluralized_name.capitalize %>Controller < Adminpanel::ApplicationController
+    end
+end

data/lib/generators/adminpanel/resource/templates/migration.rb

@@ -0,0 +1,9 @@
+class Create<%= pluralized_name.capitalize %>Table < ActiveRecord::Migration
+  	def change
+		create_table :adminpanel_<%= pluralized_name %> do |t|
+			<% fields.each do |field, type| %>
+			<%= migration_string(field, type) %><% end %>
+			t.timestamps
+		end
+ 	end
+end

data/lib/generators/adminpanel/resource/templates/resource.rb

@@ -0,0 +1,19 @@
+module Adminpanel
+    class <%= capitalized_resource %> < ActiveRecord::Base
+        attr_accessible <%= symbolized_attributes %>
+        <%= image_relationship if has_images? %>
+
+        def self.form_attributes
+            [<%= adminpanel_form_attributes %>
+            ]
+        end
+
+        def self.display_name
+            "<%= capitalized_resource %>"
+        end
+
+        # def self.icon
+        #     "icon-truck"    
+        # end
+    end
+end

data/spec/dummy/.gitignore

@@ -1,17 +1,17 @@
-# See http://help.github.com/ignore-files/ for more about ignoring files.
-#
-# If you find yourself ignoring temporary files generated by your text editor
-# or operating system, you probably want to add a global ignore instead:
-#   git config --global core.excludesfile '~/.gitignore_global'
-
-# Ignore bundler config.
-/.bundle
-/db/*.sqlite3
-/db/*.sqlite3-journal
-/log/*.log
-/tmp
-/vendor/ruby/
-.rvmrc
-.powrc
-.rspec
-
+# See http://help.github.com/ignore-files/ for more about ignoring files.
+#
+# If you find yourself ignoring temporary files generated by your text editor
+# or operating system, you probably want to add a global ignore instead:
+#   git config --global core.excludesfile '~/.gitignore_global'
+
+# Ignore bundler config.
+/.bundle
+/db/*.sqlite3
+/db/*.sqlite3-journal
+/log/*.log
+/tmp
+/vendor/ruby/
+.rvmrc
+.powrc
+.rspec
+

data/spec/dummy/README.rdoc

@@ -1,261 +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
-  |   |-- assets
-  |   `-- tasks
-  |-- log
-  |-- public
-  |-- script
-  |-- test
-  |   |-- fixtures
-  |   |-- functional
-  |   |-- integration
-  |   |-- performance
-  |   `-- unit
-  |-- tmp
-  |   `-- cache
-  |       `-- assets
-  `-- vendor
-      |-- assets
-      |   |-- javascripts
-      |   `-- 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.
+== 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
+  |   |-- assets
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   `-- cache
+  |       `-- assets
+  `-- vendor
+      |-- assets
+      |   |-- javascripts
+      |   `-- 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.