This is how I have upgraded Rails 2.3.3 to Rails 2.3.4 in Ubuntu 9.04
chee@ibm4linux:~$ sudo gem install rails
[sudo] password for chee:
Successfully installed activesupport-2.3.4
Successfully installed activerecord-2.3.4
Successfully installed actionpack-2.3.4
Successfully installed actionmailer-2.3.4
Successfully installed activeresource-2.3.4
Successfully installed rails-2.3.4
6 gems installed
Installing ri documentation for activesupport-2.3.4...
Installing ri documentation for activerecord-2.3.4...
Installing ri documentation for actionpack-2.3.4...
Installing ri documentation for actionmailer-2.3.4...
Installing ri documentation for activeresource-2.3.4...
Installing ri documentation for rails-2.3.4...
Installing RDoc documentation for activesupport-2.3.4...
Installing RDoc documentation for activerecord-2.3.4...
Installing RDoc documentation for actionpack-2.3.4...
Installing RDoc documentation for actionmailer-2.3.4...
Installing RDoc documentation for activeresource-2.3.4...
Installing RDoc documentation for rails-2.3.4...
Sunday, September 6, 2009
Announcement : Rails 2.3.4 is released on 4th Sept 2009
The Rails Team has just announced the release of Rails 2.3.4 as follows :-
We’ve released Ruby on Rails 2.3.4, this release fixes bugs and introduces a few minor features. Due to the inclusion of two security fixes, all users of the 2.3 series are recommended to upgrade as soon as possible.
We’ve released Ruby on Rails 2.3.4, this release fixes bugs and introduces a few minor features. Due to the inclusion of two security fixes, all users of the 2.3 series are recommended to upgrade as soon as possible.
Security Fixes
2.3.4 contains fixes for two security issues which were reported to us. For more details see the security announcements:Bug Fixes
Thanks to the success of the BugMash we have around 100 bug fixes as part of this release. Of particular not is the fix to reloading problems related to rack middleware and rails metals when running in development mode.New Features
Rails Basics : link_to
It is an almost Rails convention that you should use Ruby code rather than HTML to create links as a mater of style and flexibility via routes.rb
link_to is an example of a Rails function for html generation and is typically used to add site-wide navigation. For example,
<%= link_to('Home', { :action = 'index'}) %> |
<%= link_to('About Us', { :action ='about'}) %>
You may be interested to note that curly braces are optional in hashes where they are the final argument to a function as follows :-
<%= link_to('About Us',:action ='about') %>
How does one not link to a page that is currently displayed ?
<%= link_to_unless_current('Home', { :action = 'index'}) %> |
<%= link_to_unless_current('About Us', { :action ='about'}) %>
Are there other related link_to functions ?
Rails adheres to a naming convention whereby a group of related functions have related names, usually of the form original_function_name and original_function_name_with_modification
Let's check to the Rails API via the Rails API Tab in Aptana Radrails or at http://api.rubyonrails.org and this is what you should find
link_to is an example of a Rails function for html generation and is typically used to add site-wide navigation. For example,
<%= link_to('Home', { :action = 'index'}) %> |
<%= link_to('About Us', { :action ='about'}) %>
You may be interested to note that curly braces are optional in hashes where they are the final argument to a function as follows :-
<%= link_to('About Us',:action ='about') %>
How does one not link to a page that is currently displayed ?
<%= link_to_unless_current('Home', { :action = 'index'}) %> |
<%= link_to_unless_current('About Us', { :action ='about'}) %>
Are there other related link_to functions ?
Rails adheres to a naming convention whereby a group of related functions have related names, usually of the form original_function_name and original_function_name_with_modification
Let's check to the Rails API via the Rails API Tab in Aptana Radrails or at http://api.rubyonrails.org and this is what you should find
- link_to
- link_to_if
- link_to_remote
- link_to_unless
- link_to_unless_current
<%= link_to image_tag("about.gif", :border=>0), :action => 'about' %>
Wednesday, September 2, 2009
Rail Basics : What happens when you script/generate ?
chee@ibm4linux:~/workspace/crm4test$ script/generate
Usage: script/generate generator [options] [args]
Rails Info:
-v, --version Show the Rails version number and quit.
-h, --help Show this help message and quit.
General Options:
-p, --pretend Run but do not make any changes.
-f, --force Overwrite files that already exist.
-s, --skip Skip files that already exist.
-q, --quiet Suppress normal output.
-t, --backtrace Debugging: show backtrace on errors.
-c, --svn Modify files with subversion. (Note: svn must be in path)
-g, --git Modify files with git. (Note: git must be in path)
Installed Generators
Plugins (vendor/plugins): authenticated, roles
Builtin: controller, helper, integration_test, mailer, metal, migration, model, observer, performance_test, plugin, resource, scaffold, session_migration
More are available at http://wiki.rubyonrails.org/rails/pages/AvailableGenerators
1. Download, for example, login_generator.zip
2. Unzip to directory /home/chee/.rails/generators/login
to use the generator with all your Rails apps
or to /home/chee/workspace/crm4test/lib/generators/login
to use with this app only.
3. Run generate with no arguments for usage information
script/generate login
Generator gems are also available:
1. gem search -r generator
2. gem install login_generator
3. script/generate login
Usage: script/generate generator [options] [args]
Rails Info:
-v, --version Show the Rails version number and quit.
-h, --help Show this help message and quit.
General Options:
-p, --pretend Run but do not make any changes.
-f, --force Overwrite files that already exist.
-s, --skip Skip files that already exist.
-q, --quiet Suppress normal output.
-t, --backtrace Debugging: show backtrace on errors.
-c, --svn Modify files with subversion. (Note: svn must be in path)
-g, --git Modify files with git. (Note: git must be in path)
Installed Generators
Plugins (vendor/plugins): authenticated, roles
Builtin: controller, helper, integration_test, mailer, metal, migration, model, observer, performance_test, plugin, resource, scaffold, session_migration
More are available at http://wiki.rubyonrails.org/rails/pages/AvailableGenerators
1. Download, for example, login_generator.zip
2. Unzip to directory /home/chee/.rails/generators/login
to use the generator with all your Rails apps
or to /home/chee/workspace/crm4test/lib/generators/login
to use with this app only.
3. Run generate with no arguments for usage information
script/generate login
Generator gems are also available:
1. gem search -r generator
2. gem install login_generator
3. script/generate login
Rails Basics : What happens when you script/generate model ?
chee@ibm4linux:~/workspace/crm4test$ script/generate model
Usage: script/generate model ModelName [field:type, field:type]
Options:
--skip-timestamps Don't add timestamps to the migration file for this model
--skip-migration Don't generate a migration file for this model
--skip-fixture Don't generation a fixture file for this model
Rails Info:
-v, --version Show the Rails version number and quit.
-h, --help Show this help message and quit.
General Options:
-p, --pretend Run but do not make any changes.
-f, --force Overwrite files that already exist.
-s, --skip Skip files that already exist.
-q, --quiet Suppress normal output.
-t, --backtrace Debugging: show backtrace on errors.
-c, --svn Modify files with subversion. (Note: svn must be in path)
-g, --git Modify files with git. (Note: git must be in path)
Description:
Stubs out a new model. Pass the model name, either CamelCased or
under_scored, and an optional list of attribute pairs as arguments.
Attribute pairs are column_name:sql_type arguments specifying the
model's attributes. Timestamps are added by default, so you don't have to
specify them by hand as 'created_at:datetime updated_at:datetime'.
You don't have to think up every attribute up front, but it helps to
sketch out a few so you can start working with the model immediately.
This generates a model class in app/models, a unit test in test/unit,
a test fixture in test/fixtures/singular_name.yml, and a migration in
db/migrate.
Examples:
`./script/generate model account`
creates an Account model, test, fixture, and migration:
Model: app/models/account.rb
Test: test/unit/account_test.rb
Fixtures: test/fixtures/accounts.yml
Migration: db/migrate/XXX_add_accounts.rb
`./script/generate model post title:string body:text published:boolean`
creates a Post model with a string title, text body, and published flag.
Usage: script/generate model ModelName [field:type, field:type]
Options:
--skip-timestamps Don't add timestamps to the migration file for this model
--skip-migration Don't generate a migration file for this model
--skip-fixture Don't generation a fixture file for this model
Rails Info:
-v, --version Show the Rails version number and quit.
-h, --help Show this help message and quit.
General Options:
-p, --pretend Run but do not make any changes.
-f, --force Overwrite files that already exist.
-s, --skip Skip files that already exist.
-q, --quiet Suppress normal output.
-t, --backtrace Debugging: show backtrace on errors.
-c, --svn Modify files with subversion. (Note: svn must be in path)
-g, --git Modify files with git. (Note: git must be in path)
Description:
Stubs out a new model. Pass the model name, either CamelCased or
under_scored, and an optional list of attribute pairs as arguments.
Attribute pairs are column_name:sql_type arguments specifying the
model's attributes. Timestamps are added by default, so you don't have to
specify them by hand as 'created_at:datetime updated_at:datetime'.
You don't have to think up every attribute up front, but it helps to
sketch out a few so you can start working with the model immediately.
This generates a model class in app/models, a unit test in test/unit,
a test fixture in test/fixtures/singular_name.yml, and a migration in
db/migrate.
Examples:
`./script/generate model account`
creates an Account model, test, fixture, and migration:
Model: app/models/account.rb
Test: test/unit/account_test.rb
Fixtures: test/fixtures/accounts.yml
Migration: db/migrate/XXX_add_accounts.rb
`./script/generate model post title:string body:text published:boolean`
creates a Post model with a string title, text body, and published flag.
Subscribe to:
Posts (Atom)