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.

warden-github-rails

warden-github-rails allows you to use GitHub as authorization and more. Use organizations and teams as means of authorization by simply wrapping your rails routes in a block. Also useful to get a user’s details through OAuth.

Sounds really cool!

Building JSON APIs in Rails 5 today!

An article I wrote about building JSON APIs in Rails 5… today! How you can try out Rails 5 using the new –api version, which gives you a scaled down, API specific version of Rails functionality. This article also covers some caching and middleware request throttling.

Link is broken. Correct link: http://blog.codeship.com/building-a-json-api-with…

Rails Interactor Pattern - Part 2

This time I’m adding some helper methods to our interactor, which will make handling failure cases easier and more obvious. Here’s the link to part 2 or first catch up with part 1.

Image Processing in Rails using AWS Lambda

A common problem with image processing Rails apps has been the excessive memory consumption within the worker processes. When images are large enough, our worker will consume a big portion of our memory and will take forever to finish. If you are deploying on Heroku, you will probably be paying for the cheapest worker and the R14 notification emails will be flooding your inbox. Learn the solution here

CrashBreak: A new approach for dealing with production exceptions and bugs in Ruby

Hello! Some time ago I was working on an application that had many bugs and reproducing each one was time consuming. I thought about making this process faster and more user-friendly. Recreating bugs manually in the browser by typing data and setting all connected modules in the same way like when the exception occurred can be annoying. Also, there is no certainty that the bug is reproduced in the same way it occurred. The other problem is that many of the bugs are hard to reproduce and connected to different layers of the system. The idea of CrashBreak is to reproduce the exception from the staging server on the programmer’s computer by running a request test. In order to do this the library needs to dump your system piece by piece. Currently we have 3 dumpers: for database, all request data (headers, url, body) and user session. We tried to create the whole system in an adaptive way. It means that you can write your own extensions to adapt the library to your needs. The beta of the service is ready and available at Please give it a try and send me your feedback so I can make CrashBreak even better. Thank you kind strangers! Michał Janeczek

1) the link does not work because of the dot at the end 2) wait… what? So it wo…
Hi! Of course not! You are able to dump your database and send it whereve…

Create Ruby Gem by Example

Learn how to build a Ruby gem by creating one

@IGOR why is that? That is the TV show to be queried.
I believe Igor is just pointing out the ruby convention to use snake case varia…
because of this https://github.com/bbatsov/ruby-style-guide …
@IGOR & @HANSEN noted, thanks for the pointer. Besides that, how did you fi…
Loading older posts