RubyFlow The Ruby and Rails community linklog

×

The Ruby and Rails community linklog

Made a library? Written a blog post? Found a useful tutorial? Share it with the Ruby community here or just enjoy what everyone else has found!

Submit a post

You can use basic HTML markup (e.g. <a>) or Markdown.
Note that your post may be edited to suit the format of the site.

As you are not logged in, you will be
directed via GitHub to signup or sign in

Post Preview

Note: Only the first pargraph is shown on the front page and overly long paragraphs may be broken up.

Rails' rescue_from

A little write up on rescue_from: rescue_from

Nice! Didn’t know about ActiveSupport::Rescuable But I think using a private me…
It piles the handlers up anyway so even if you use a block in your ApplicationC…

Integrating your rails app with Dropbox

At thredUP, we recently started using dropbox to do more than just store and share files among employees. We’ve now integrated it with a couple of our applications so that certain data sets get archived there. We used to just send them by email if they were small enough or save them to a server and then download them manually. Now, with dropbox, they get dropped in a shared folder and the people that need access, have it. Implementing this integration had a couple hiccups along the way and I want to share how we did it.

Serving ruby gems, the paranoid way

As I wrote in a previous blog post, there are good reasons to be paranoid with Ruby gems: they may have been hacked and “enhanced” with malicious code. It would be great if we could check every gem that we want to install, including their dependencies. You may think “this is not practical at all”, and you are probably right. But still, I wanted to give this idea a try and learn about the challenges that people will face if they want to review their gems before installation. Read More

Loading older posts