"Rails Installation on windows"

Problem : JSON not installable on WINDOWS , when we do bundle install

Solution :

Assuming you have Ruby and Ruby gems installed
 
> my current platform: ruby-1.8.6. From the command prompt, type:
gem install pik
> After the successful installation of pik, type:
pik_install C:tools
> Add this to your Path Environmental variables (My Computer > Right Click > Properties > Advanced System Settings > Environmental Variables > Path)

Once you’re done. Open a new command prompt and type:
pik list
It will add the current version of ruby into the list.
Now what’s so special about pik? How it can handle the multiple versions? To see that in action, in command prompt, type:
pik install ruby 1.8.7
pik install ruby 1.9.2
Similarly you can do for 1.9.2

pik list
It will show you the current version of ruby and the other ones.

pik use 187
or
pik use 192

depending on which version to use

ruby -v
now you can have multiple ruby versions on windows also

Time to install Ruby Devkit

Download  – http://rubyinstaller.org/downloads/

Install under C:/devkit

After extraction, open your command, go inside C:devkit prompt and type:
ruby dk.rb init
This will create the config.yml inside C:/devkit. Now you need to define all the Ruby versions inside that file, so that devkit will create native extensions for them. To do that, open that file and at the end of it, write these lines:
– C:ruby
– C:UsersPC-name.pikrubiesRuby-187-p330
– C:UsersPC-name.pikrubiesRuby-192-p0
Once done save it and from the command prompt, type:
ruby dk.rb install

Now you can do
your bundle install
or rails install

and it should work properly

"Rails Installation on windows"

"Rails in now 4.0 BETA"

The forthcoming 3.2.x release series will be the last branch of Rails that supports Ruby 1.8.7. There’s a new 3-2-stable branchin git to track the changes we need until 3.2.0 final is release and for managing point releases after that.

So for now you should stop floating on rails/master if your application is not compatible with Ruby 1.9.3. We have updated the version numbers to indicate this backwards incompatibility to be 4.0.0.beta. This doesn’t mean that 4.0 is anywhere close to being released, mind you. We’re simply doing this now because we’re dropping support for Ruby 1.8.7 in rails/master and people should know what’s up.

Major versions of Rails has been on about 2-year release cycle since 1.0 (released in 2005, followed by 2.0 in 2007, followed by 3.0 in 2010) and we intend to continue this pattern. The current internal target for Rails 4.0 is sometime in the Summer of 2012 — but we have blown every major release estimate in the past, so don’t bet your farm on it.

There’s not a lot of details about what we’re going to include in Rails 4.0 yet as the primary purpose for bumping the major version number is to drop Ruby 1.8.7 support. But unlike Rails 3.0, we intend for it to be a much smoother transition. The intention is not for this to be a REWRITE EVERYTHINGrelease in the same way 3.0 was to some extent.

But we’re getting ahead of ourselves. First mission is to get Rails 3.2 out!

Source : http://weblog.rubyonrails.org/2011/12/20/rails-master-is-now-4-0-0-beta

"Rails in now 4.0 BETA"

"Rails Installer: Ruby and Rails on Windows in a Single, Easy Install"

RailsInstaller is a new project from Wayne E Seguin (of RVM fame) that brings RubyInstaller-style simplicity to getting Ruby and Rails set up on Microsoft Windows (XP, Vista, or 7). In a single wizard-driven installation you get Ruby 1.8.7-p330 (with DevKit), Rails 3.0.3, Git, and SQLite 3.

Rails Installer was developed with help from Luis Lavena (a Ruby on Windows expert) and Dr. Nic Williams (Engine Yard’s resident Australian comedian) and its release comes just weeks after Wayne was (re)hired by Engine Yard to work on new open source initiatives.

To get started, go to railsinstaller.org, download the “Rails Welcome Kit” and run the installer. There’s a screencast you can watch too. The process is as simple as it sounds and you can have a basic, empty Rails project running within minutes.

If you want to follow along more, check out the @RailsInstaller Twitter account or theRails Installer Google Group / mailing list.

"Rails Installer: Ruby and Rails on Windows in a Single, Easy Install"

"Ruby, Ruby on Rails Support Discontinued in NetBeans IDE"

Dear NetBeans Community: 

After thorough consideration, we have taken the difficult step to discontinue support for Ruby and Ruby on Rails in the NetBeans IDE. Two main issues underpin this decision: 

Java SE 7 and Java Development Kit 7 (JDK 7) are the next major releases of the Java SE platform, which Oracle is committed to deliver in 2011. A key objective of the NetBeans IDE has always been to offer superior support for the Java platform. To maintain that objective and capitalize on the JDK 7 release themes–multi-language support, developer productivity and performance–it is necessary that our engineering resources are committed to a timely and quality release of NetBeans IDE 7.0. 

Second: Although our Ruby support has historically been well received, based on existing low usage trends we are unable to justify the continued allocation of resources to support the feature. 

As of January 27, the Ruby module will be gone from development builds of NetBeans IDE 7.0. Developers who want to continue to use Ruby and Ruby on Rails functionalities in the NetBeans IDE should please visit the NetBeans Ruby Support page for details on how to do so going forward. 

We remain committed to delivering a first-class product to our community of developers and users, and we encourage your feedback on our mailing lists and forums, on Twitter, or by writing to us. 

Thank you for your continued support of NetBeans.
The NetBeans Team

Source : http://netbeans.org/community/news/show/1507.html


"Ruby, Ruby on Rails Support Discontinued in NetBeans IDE"

"csrf token warning fix"

csrf token warning fix

Solution:
1/ add this to your layout

<%= javascript_tag “var AUTH_TOKEN = #{form_authenticity_token.inspect};” if protect_against_forgery? %>
    <%= csrf_meta_tags %>

Add this to your controller
skip_before_filter :verify_authenticity_token

2/ comment out  protect_from_forgery from your application controller .

"csrf token warning fix"