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 3.18.2011: Rails Bridge

Will Read
Friday, March 18, 2011

Interesting Things

  • Rails Bridge is hosting an event here at Pivotal Labs to teach people how to develop Rails applications (including TDD and source control!). The students are designers, bootstrapping startups and those who are just curious. THIS EVENT NEEDS VOLUNTEERS! Come teach their well-laid out lesson plan, OR if you’re not up for teaching, come and help out with the install-fest Friday night. The dates are March 25th for the install-fest and March 26 for the actual class.
    Here’s the deets on Meetup
    Here’s the volunteer page
  • 0 Shares
  • Share on Facebook
  • Share on Twitter

3 Comments

  1. KJ says:

    The event isn’t for teaching “people”, it’s exclusive of men.

    March 18, 2011 at 8:26 pm

  2. Will Read says:

    KJ, that’s not 100% true. Men are welcome to come, but they must be the guest of an attending lady. There’s historically been more guys at this workshop than you might think.

    March 18, 2011 at 10:12 pm

  3. Muralidharan K says:

    i read Linkedin articles using ROR

    http://pivotallabs.com/users/will/blog/articles/1096-linkedin-gem-for-a-web-app.

    This articles helped me to achieve some of practice. It is working on local environment but it doesn’t work on production.

    I got following error : -

    A OAuth::Problem occurred in social#new_linkedin:

    timestamp_refused
    [RAILS_ROOT]/vendor/gems/oauth-0.4.3/lib/oauth/consumer.rb:181:in `request’

    * Parameters: {“network”=>["linkedin"], “action”=>”new_linkedin”, “hub_id”=>”971406986″, “controller”=>”social”, “alias_name”=>”ggggg”, “count”=>”1″}

    ——————————-

    [RAILS_ROOT]/vendor/gems/oauth-0.4.3/lib/oauth/consumer.rb:181:in `request’
    [RAILS_ROOT]/vendor/gems/oauth-0.4.3/lib/oauth/consumer.rb:197:in `token_request’
    [RAILS_ROOT]/vendor/gems/oauth-0.4.3/lib/oauth/consumer.rb:139:in `get_request_token’
    [RAILS_ROOT]/lib/linked_in/authorization_helpers.rb:21:in `request_token’
    [RAILS_ROOT]/app/controllers/social_controller.rb:195:in `new_linkedin’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:1162:in `send’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:1162:in `perform_action_without_filters’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/filters.rb:580:in `call_filters’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/filters.rb:573:in `perform_action_without_benchmark’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue’
    /usr/lib/ruby/1.8/benchmark.rb:293:in `measure’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/rescue.rb:201:in `perform_action_without_caching’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:13:in `perform_action’
    [RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in `cache’
    [RAILS_ROOT]/vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in `cache’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:12:in `perform_action’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:529:in `send’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:529:in `process_without_filters’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/filters.rb:569:in `process_without_session_management_support’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/session_management.rb:130:in `process’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/base.rb:389:in `process’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:149:in `handle_request’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:107:in `dispatch’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:104:in `synchronize’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:104:in `dispatch’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:120:in `dispatch_cgi’
    [RAILS_ROOT]/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:35:in `dispatch’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:76:in `process’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:74:in `synchronize’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/rails.rb:74:in `process’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:159:in `process_client’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `each’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:158:in `process_client’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `initialize’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `new’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:285:in `run’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `initialize’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `new’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:268:in `run’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:282:in `run’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:281:in `each’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/configurator.rb:281:in `run’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:128:in `run’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel/command.rb:212:in `run’
    /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/mongrel_rails:281
    /usr/bin/mongrel_rails:19:in `load’
    /usr/bin/mongrel_rails:19

    Please advice me.

    Thanks
    Murali

    April 25, 2011 at 1:44 am

Add New Comment Cancel reply

Your email address will not be published.

Will Read

Will Read
San Francisco

Recent Posts

  • Cucumber: When to Use It, When to Lose It
  • Org Chart Growth and Keeping Our “Flatness”
  • Releasing When It’s Ugly
Subscribe to Will's Feed

Author Topics

bloggerdome (4)
cucumber (1)
pm (1)
testing (4)
agile (31)
process (1)
"soft" ware (16)
feedback (1)
engines (1)
documentation (1)
tdd (2)
bdd (1)
breakfast (1)
pairing (1)
api (2)
bug (1)
chore (1)
velocity (1)
oauth (1)
queues (3)
version control (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 >