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

SF Standup 9/13/2011: Tempfiles, Rails3.1 Asset Pipeline and Ruby Kids

Ryan Dy
Tuesday, September 13, 2011

Help

  • Tempfiles created by paperclip or similar ruby gems don’t seem to get cleaned up. Is it best to monkey patch the use of the tempfiles and make sure unlink is called? Is it better to create a cron job that inspects tempfiles that haven’t been touched for awhile and clean them up?

Interesting

  • If you are migrating from a Rails 3.1 release candidate you might need to generate a new production.rb file that configures that asset pipeline in production differently. Also, if you are using Capistrano 2.80 you should: load ‘deploy/assets’ in your deploy.rb file. This will do the proper compilation and copying of assets in your shared release folder. Check out the asset pipeline guide.
  • Kids Ruby is have an event in cooperation with Gogaruco at Pivotal Labs this Sunday from 12-2. Register for it here.
  • 0 Shares
  • Share on Facebook
  • Share on Twitter

One comment

  1. Peter Jaros says:

    > Is it best to monkey patch the use of the tempfiles and make sure unlink is called?

    How about real-patching the use of tempfiles?

    September 27, 2011 at 4:56 am

Add New Comment Cancel reply

Your email address will not be published.

Ryan Dy

Ryan Dy
San Francisco

Recent Posts

  • SF Standup 03/14/2012: Capybara and push state
  • SF Standup 06/15/2011: Ruby 1.9.2patched and iScroll
  • SF Standup 06/13/2011: Ackmate and UTF8
Subscribe to Ryan's Feed

Author Topics

gem (1)
gplv2 (1)
qt (1)
ruby (2)
iscroll (1)
mobile (1)
require (1)
textmate (1)
gogaruco (1)
amazon s3 (1)
desert (1)
ide (1)
rspec (1)
rubymine (1)
taste (1)
uploads (1)
agile (1)
css (1)
firebug (1)
js (1)
yui (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 >