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.

Concerned about Code Reuse?

If you’re concerned about code reuse in Ruby you should be using Active Support concerns to awesome-ize your modules. Learn why and how in this quick article.

Rails’ Concern class is just a big fat red flag that Ruby ought to make module …
Pretty cool! Didn’t know about this one. Thanks schneems
It would be great if something like concerns could be brought into Ruby core. …
@schneems In your intro above, I think you mean “ActiveSupport concerns”, not “…

Learning Grails - A beginners guide for the Rails developer

I have started working on a book called “Learning Grails - A beginners guide for the Rails developer” http://leanpub.com/learninggrails). Rapid MVC development strongly influenced by Rails.

This is a cool idea, a TOC and maybe a sample page might be a good addition tho…
Thanks! I’ll get that up soon. The TOC is pretty much hammered out, but there a…

Devise, CanCan and Twitter Bootstrap for Rails: Tutorial and Example App

Just added to the RailsApps GitHub repo: an example app for Rails, Twitter Bootstrap, Devise, and CanCan. Twitter Bootstrap is coming on strong as a front-end framework to use with Rails; Devise continues to be popular for user management and authentication; and CanCan is a favorite for authorization architecture. This example app puts them together. Best of all, it comes with a detailed Rails Tutorial for Devise with CanCan and Twitter Bootstrap. The tutorial takes up where the popular RailsApps tutorial for Devise with RSpec and Cucumber leaves off. Like the other example apps in the RailsApps repo, this one comes with an application template to generate a starter app, with options for Haml, Devise modules, and more. Built with the Rails Apps Composer gem.

awesome…….

Ruby on Rails: Helping the CX Cloud Run Smoothly

Here at the CX cloud (get your first 10GB free!), we love Ruby on Rails for its adaptability within our service. Check out our blog on why we use it in our cloud storage here: https://blog.cx.com/cloud-storage-news/ruby-on-rails/

“That’s why we use Ruby on Rails, a programming language that enables developme…
Think I’ll file this one under “shameless self-promotion”. The content of this …

Sadie, Olsen - Data gathering and reporting

I’ve released a couple of data-gathering and reporting gems: Sadie and Olsen. Sadie makes it easy to assemble data from various databases, network locations, files and other sources. It has some nice facilities for managing memory usage, session storage, and optimal and/or minimal execution. Olsen, a simple reporter, builds on Sadie to form a framework for reporting and analysis. It currently uses the TeX typesetting system to produce pdfs, but it is completely pluggable and can be easily extended to produce a number of different outputs.

Gon gem version 3.0.0 is out

I just finished refactoring and updating of my gon gem and now it can rock from any part of your application with Gon.global feature.

Is this a good idea? I am afraid it defeats the purpose of MVC.
Hello, thanks for commenting. If you meant gon.global - I think it’s fine for c…

Redis Failover for Ruby based on ZooKeeper

I just launched redis_failover for Ruby. It’s a full redis failover solution based on ZooKeeper that consists of a Node Manager and a failover client. A redis failover Node Manager daemon runs as a background process and monitors all of your configured master/slave nodes. The client also acts as a load balancer in that it will automatically dispatch Redis read operations to one of N slaves, and Redis write operations to the master. If it fails to communicate with any node, it will go back and fetch the current list of available servers, and then optionally retry the operation.

Loading older posts