A gem that makes it easy to prevent server side request forgery (SSRF) attacks

Efficiently render JSON API documents.

LittlePlugger is a module that provides Gem based plugin management. By extending your own class or module with LittlePlugger you can easily manage the loading and initializing of plugins provided by other gems.

Instrumentation for GitLab

Adds methods to ActiveRecord::Migration to create and manage database views in Rails

Library for validating urls in Rails.

JSON API(jsonapi.org) serializer that works with rails and can be used to serialize any kind of ruby objects

A wonderfully simple way to load your code

LicenseFinder works with your package managers to find dependencies, detect the licenses of the packages in them, compare those licenses against a user-defined list of permitted licenses, and give you an actionable exception report.

A Parsing Expression Grammar (PEG) Parser generator DSL for Ruby

Run Selenium tests more easily with install and updates for all supported webdrivers.

OAuth 2.0 Server & Client Library. Both Bearer token type are supported.

A library for interacting with Xcode simulators.

Unobtrusive nested forms handling, using jQuery. Use this and discover cocoon-heaven.

Easily test email in RSpec, Cucumber, and MiniTest

Easily test email in RSpec, Cucumber, and MiniTest

A really Ruby Mail handler.

Easiest way to manage multi-environment settings in any ruby project or framework: Rails, Sinatra, Padrino and others

Have you ever wanted to call <code>exit()</code> with an error condition, but weren't sure what exit status to use? No? Maybe it's just me, then. Anyway, I was reading manpages late one evening before retiring to bed in my palatial estate in rural Oregon, and I stumbled across <code>sysexits(3)</code>. Much to my chagrin, I couldn't find a +sysexits+ for Ruby! Well, for the other 2 people that actually care about <code>style(9)</code> as it applies to Ruby code, now there is one! Sysexits is a *completely* *awesome* collection of human-readable constants for the standard (BSDish) exit codes, used as arguments to +exit+ to indicate a specific error condition to the parent process. It's so fantastically fabulous that you'll want to fork it right away to avoid being thought of as that guy that's still using Webrick for his blog. I mean, <code>exit(1)</code> is so passé! This is like the 14-point font of Systems Programming. Like the C header file from which this was derived (I mean forked, naturally), error numbers begin at <code>Sysexits::EX__BASE</code> (which is way more cool than plain old +64+) to reduce the possibility of clashing with other exit statuses that other programs may already return. The codes are available in two forms: as constants which can be imported into your own namespace via <code>include Sysexits</code>, or as <code>Sysexits::STATUS_CODES</code>, a Hash keyed by Symbols derived from the constant names. Allow me to demonstrate. First, the old way: exit( 69 ) Whaaa...? Is that a euphemism? What's going on? See how unattractive and... well, 1970 that is? We're not changing vaccuum tubes here, people, we're <em>building a totally-awesome future in the Cloud™!</em> include Sysexits exit EX_UNAVAILABLE Okay, at least this is readable to people who have used <code>fork()</code> more than twice, but you could do so much better! include Sysexits exit :unavailable Holy Toledo! It's like we're writing Ruby, but our own made-up dialect in which variable++ is possible! Well, okay, it's not quite that cool. But it does look more Rubyish. And no monkeys were patched in the filming of this episode! All the simpletons still exiting with icky _numbers_ can still continue blithely along, none the wiser.

Expand the 'vagrant box' command to support the creation of base boxes from scratch