Close
Glad You're Ready. Let's Get Started!

Let us know how we can contact you.

Thank you!

We'll respond shortly.

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

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.

Comments
  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?

Post a Comment

Your Information (Name required. Email address will not be displayed with comment.)

* Copy This Password *

* Type Or Paste Password Here *