RubyFlow : The Ruby Community Blog

Home   Submit   Sign Up   Log In   leaders   Twitter   RSS Feed  
 

DanielKehoe — 13 posts

http://danielkehoe.com/

Ruby 1.9.3-p125 is released, the new recommended Ruby version, available via rvm.

Update Ruby with "rvm install ruby-1.9.3-p125" and also "gem update rake" to 0.9.2.2.
Heroku offers Ruby 1.9.2 as a default with its newest stack. But did you know you can use Ruby 1.9.3 (Ruby's current recommended stable release)? Here's how to set up an app with Rails 3.2 and Ruby 1.9.3 on Heroku. See Deploying Rails 3.2 with Ruby 1.9.3 on Heroku.
Guide to Installing Rails 3.2  railsapps.github.com
Detailed instructions (with advice) on how to install the latest release of Rails 3.2. See a Guide to Installing Rails 3.2.
Rails v3.2.1 has been released to provide minor fixes to the previous release. See the Ruby on Rails v3.2.1 Changelogs.
My RailsApps tutorials and starter apps have been well-received (thanks!) and today I completed a new one. You can find the example app for Rails 3.1 Subdomains in the GitHub repo. The Rails 3.1 Subdomains Tutorial is in the GitHib wiki and you can find an application template for a Rails starter app on GitHub as well. The example app shows how to build an app with "Basecamp-style" use of subdomains using Mongoid for a datastore and Devise for authentication. As always, please try it, copy, fork and submit issues so all may benefit.
It's easy to create a new Rails application using "rails new myapp". But after that, what do you do? What gems do you always add? What decisions do you make before beginning development? What important items are often overlooked before deploying an app? I'd like to put together a reference checklist to share. Any suggestions? I've asked on Stack Overflow: Checklist for starting a new Rails application?
I've just written a Guide to HTML5 Boilerplate for Rails Developers. HTML5 Boilerplate serves as a useful reference for Rails developers who want to provide structure and convention for the HTML, CSS, and Javascript of an application’s front-end. But not all of HTML5 Boilerplate is useful for a Rails developer. With this guide you can pick and choose the components that are useful for a Rails application.
Example Apps for Rails 3.1  railsapps.github.com
Examples (with walk-through tutorials) for Rails 3.1 using Devise (authentication), OmniAuth (authentication), RSpec, Cucumber (BDD), Mongoid (NoSQL datastore). Useful as starter apps or reference implementations.

Rails 3.1 example apps
A Guide to Installing Rails 3.1  railsapps.github.com
Detailed instructions on how to install Rails 3.1 with advice and troubleshooting tips:

A Guide to Installing Rails 3.1
Detailed (and current) instructions on how to install Rails 3.1. Suggests upgrading to RubyGems 1.8.5 and Rake 0.9.1 (and shows how). Points out a problem with "gem install rails --pre". With other surprises, advice, and troubleshooting tips.
Daniel Kehoe's detailed tutorial and example code for OmniAuth and Mongoid shows how to build a complete Rails 3 example app with OmniAuth and Mongoid. OmniAuth manages authentication using Twitter, Facebook, or many other service providers. MongoDB is used as a datastore with the Mongoid gem for quick development without schemas or migrations. This tutorial also gives you the option of using jQuery, Haml, RSpec and Cucumber, showing how to integrate each option. In addition to the tutorial, Kehoe provides a Rails application template you can use to generate a fully-functional starter app in minutes. Kehoe's previous tutorials and example apps have been popular (as can be seen by the number of watchers and forks on GitHub) and include starter apps for "Mongoid and Devise" and "Devise with Subdomains".
(with a detailed walk-through tutorial) that shows how to set up subdomains in Rails 3 using Devise for authentication:

Rails 3 Subdomains Devise

The tutorial goes into detail about the how to set up the app to maintain sessions across subdomains.
On GitHub: rails3 mongoid devise example app and tutorial. With an application template generator so anyone can use the example as a beginning point for a new Rails app. Options for Haml and Heroku.