Sarah will give a Ruby introduction class for kids at RubyConf. However, there won’t be any Internet connection available, but the participants will need to install several gems.
A solution to this problem is the gem geminabox which allows you to run a server providing gems. Other users who have geminabox installed then are able to install gems from that server.
We’ve completed the hosting move, and Pivotal Tracker is back up. We’ll post more details about the new environment within the next few days.
In the meantime, if you experience any problems, please try clearing your browser’s cache as well as all cookies for the pivotaltracker.com and www.pivotaltracker.com domains. If the issue persists, please let us know!
We have begun the hosting move, and anticipate the entire process to take approximately 6 hours. For most up to date status, please follow @pivotaltracker.
In the continued saga that is the Rails 2.3.10 to Rails 3.0.1 upgrade, I found this little nugget today…you want to add a custom action to a controller that inherits from a Devise controller. Here are the steps that you need to follow:
1) Create a custom controller that overrides some out of the box Devise actions as well as adds a new method.
class RegistrationsController < Devise::RegistrationsController
def update
# do something different here
end
def deactivate_owner
# deactivate code here
end
end
2) You have to tell Devise to use the new controller in routes.rb as well as add the new route to the new action.
devise_for :owners, :controllers => { :registrations => "registrations" } do
post "deactivate_owner", :to => "registrations#deactivate_owner", :as => "deactivate_owner_registration"
end
When we initially implemented this, our route definition looked like this:
post "deactivate_owner", :to => "registrations#deactivate_owner", :as => "deactivate_owner_registration"
devise_for :owners, :controllers => { :registrations => "registrations" }
When it was implemented this way, we kept getting a AbstractController::ActionNotFound exception. Once we passed the block to devise_for seen in #2, everything worked fine.
As a popular web rendering engine, WebKit is mostly used via browsers. Sencha Engineering Director Ariya Hidayat presents a different angle: using WebKit as a library to write web development tools. Includes how to get and compile the WebKit code.
See all our talks at http://pivotallabs.com/talks
CrowdFlower enables a quality, fast, large, global workforce to complete simple tasks. Brian O’Rourke and Chris Van Pelt create a sample app to demonstrate the API and the quality analysis tools. They also discuss lessons learned in its development.
See all our talks at http://pivotallabs.com/talks
As a popular web rendering engine, WebKit is mostly used via browsers. Sencha Engineering Director Ariya Hidayat presents a different angle: using WebKit as a library to write web development tools. Includes how to get and compile the WebKit code.
CrowdFlower enables a quality, fast, large, global workforce to complete simple tasks. Brian O’Rourke and Chris Van Pelt create a sample app to demonstrate the API and the quality analysis tools. They also discuss lessons learned in its development.
bundle install --without test excludes the test group in your Gemfile from the install. It works well for reducing the size of your Heroku slug. However, there’s a glitch with this option on Heroku — when you specify it, Heroku reinstalls every included gem every time you deploy. It does respect your Gemfile.lock, so you’re trading a smaller slug for a longer deploy.
Pivotal’s open source CIMonitor project now supports OpenID! Thanks Tyler and Josh.
Arel has a bug that makes it difficult to use in rails console. Every time you add a predicate, the number of internal objects in the Arel result increases exponentially. So, by the time you have 5 or 6 predicates, the console finishes generating the expression more or less instantly, and then spends 15+ minutes calling to_s on the resulting Arel object in order to display it to you. tl;dr: when you’re playing with Arel in rails console, end every line with ; nil to avoid having it print out the result. The exponential object explosion will be fixed in Rails 3.1.
While helping client upgrade a Rails 2.3.10 site to Rails 3.0.1, I came across a very perplexing problem with our WebDriver based Cucumber tests that all worked fine under 2.3.10.
We were “randomly” getting some very strange errors from Cucumber having to do with timeout problems and other strangeness like Cucumber not being able to find form fields to fill in.
The solution:
1) require => false for the FakeWeb line in the Gemfile
2) add require ‘fakeweb’ to the top of the test_helper.rb file
or optionally scrap FakeWeb for either Artifice or WebMock
It has something to do with FakeWeb inserting it into the HTTP stack strangely even if you tell it to allow non-local HTTP requests. We weren’t seeing it in 2.3.10 because we were using a cucumber environment to run the cucumber tests. Now under 3.0.1 we run the cucumber tests in the test environment.
I wish I had some more details but I was just happy to move past this strangeness so I didn’t really look back.