The rubber plugin enables relatively complex multi-instance deployments of RubyOnRails applications to Amazon's Elastic Compute Cloud (EC2). Like capistrano, rubber is role based, so you can define a set of configuration files for a role and then assign that role to as many concrete instances as needed. One can also assign multiple roles to a single instance. This lets one start out with a single ec2 instance (belonging to all roles), and add new instances into the mix as needed to scale specific facets of your deployment, e.g. adding in instances that serve only as an 'app' role to handle increased app server load.

Rails controllers for Stripe Checkout Sessions and Webhooks

Common layout and functionalities for NoCMS custom admins

This engine allow adding content blocks to other AR model with very few dependencies.

Gem with content page functionality independent from any CMS and embeddable in any Rails 4 app

NoPassword is a Ruby on Rails gem that allows session authentication with a token or a magic link via an email sent to the user; there is no need for a password.

【react&rails】notee is creating CMS(blog) gem by only one command.

Notifiable engine for Rails.

This project intend to offer a full notification system, back and front-end.

Asset pipeline bundling of the nvd3-community library.

Opinionated Rails project templating: rspec, haml, sass, compass, etc

Engine providing key-value settings stored in db with a web UI.

Nyanko is a Rails extension tool deeply inspired from Chanko

Simple and modulable authentication gem

Rails gem that allows you to easily interact with an Oauth secured rest API with the ActiveResource model.

Make your ActiveRecord IDs non-obvious

Simple Rails plugin to obfuscate strings in views.

Occams is a powerful Rails 6.1-7.1+ CMS Engine

== OceanDynamo As one important use case for OceanDynamo is to facilitate the conversion of SQL databases to no-SQL DynamoDB databases, it is important that the syntax and semantics of OceanDynamo are as close as possible to those of ActiveRecord. This includes callbacks, exceptions and method chaining semantics. OceanDynamo follows this pattern closely and is of course based on ActiveModel. The attribute and persistence layer of OceanDynamo is modeled on that of ActiveRecord: there's +save+, +save!+, +create+, +update+, +update!+, +update_attributes+, +find_each+, +destroy_all+, +delete_all+, +read_attribute+, +write_attribute+ and all the other methods you're used to. The design goal is always to implement as much of the ActiveRecord interface as possible, without compromising scalability. This makes the task of switching from SQL to no-SQL much easier. OceanDynamo uses only primary indices to retrieve related table items and collections, which means it will scale without limits. OceanDynamo is fully usable as an ActiveModel and can be used by Rails controllers. Thanks to its structural similarity to ActiveRecord, OceanDynamo works with FactoryBot. See also Ocean, a Rails framework for creating highly scalable SOAs in the cloud, in which ocean-dynamo is used as a central component: http://wiki.oceanframework.net

A rails helper that makes including svg Octicons simple.