Pivotal Labs

Main menu

Skip to primary content
Skip to secondary content
  • About
  • Case Studies
  • Team
    • Executives
    • Locations
      • San Francisco (HQ)
      • Boston
      • Boulder
      • Denver
      • London
      • Los Angeles
      • New York
  • Community
    • Blogs
    • Tech Talks
    • Events
  • Careers
    • Lifestyle
    • Principles & Practices
    • Benefits
    • FAQ
    • Apply
  • Contact
    • Press Room
    • Press Releases
    • In The News
    • Press Kit
  • All
  • Labs
  • Standup
  • Tracker

Standup 12/17/2008 Asset Host & Retardation Inhibitor

Colin Shield
Thursday, December 18, 2008

Ask for Help

“How can asset_host and retardation_inhibitor could work together nicely?”

ActionController::Base.asset_host

Tells your Rails application to generate external resources’ links pointing to the host of your choosing.

The general opinion was that any sophistication should be handled by asset_host configurations in the appropriate rails environment files.

This lead to the sticky problem of our CI process running the Selenium tests in the development environment rather than the test environment. The asset_host using the development environment configuration rather than the test environment.

Everyone agreed that this wasn’t the best way to run the selenium tests.

A desperate request to rename the Pivotal project “retardation_inhibitor” met with no resistance, much to the delight of the Pivot responsible for explaining it’s usefulness.

“New Relic & Desert?”

Ruby & Rails can sometimes appear to be moving so quickly that not advancing feels like standing still. A project found problems with the latest versions of New Relic and Desert.

Every page request resulted in a stack trace in the log.

The general consensus was that the latest version of New Relic would solve this problem. Of course the team had already tried this along with several other versions.

Some Pivots in New York had apparently encountered and solved similar problems. Hopefully they can help out.

Another Pivotal project had similar problems and had to upgrade to 2.7.3. They used these update steps.

http://sites.google.com/a/newrelic.com/rpm-docs/installing-the-agent.

They originally tried to just install the latest without following the steps outlined in the link above and still had problems.

Interesting Things

Look out for a public Pivotal Pulse announcement soon.

  • 0 Shares
  • Share on Facebook
  • Share on Twitter

One comment

  1. Joseph Palermo says:

    The NewRelic problem was solved by putting this before rails in environment.rb:

    module NewRelic; end

    December 18, 2008 at 9:48 pm

Add New Comment Cancel reply

Your email address will not be published.

Colin Shield

Colin Shield
San Francisco

Recent Posts

  • Database.yml files using Chef Server
  • Standup Oct/19/2010: Cedar, a BDD Testing Framework for Objective C
  • Donkey & Goat Open House
Subscribe to Colin's Feed

Author Topics

chef server (1)
agile standup (2)
performance (1)
  • About
  • Case Studies
  • Team
  • Community
  • Careers
  • Contact
  • Labs
  • Events

Contact Us

contact@pivotallabs.com
+1 415-77-PIVOT
TwitterLinkedInFacebook

Pivotal Tracker

Tracker is the award-winning agile project management tool that enables real-time collaboration around a shared, prioritized backlog.
Visit pivotaltracker.com >