`versioned-routes-rails` adds a single method to the Rails `routes.rb` DSL,`version`, which allows you to specify API versions.

Easily manage a version number for your Rails app. The version is stored in a YAML file within your app.

The premise of this gem is that consumers of your API need versioning and different shapes of your resources. Without proper thought into versioning and shaping, your codebase can quickly resolve into a redundant and confusing state. This gem tries to solve that problem by allowing the API owner to use simple conventions -- Accept headers and ActiveModelSerializer namespacing -- to achieve controller reuse by controllers delegating resource versioning and shaping to the serializer level.

We've taken the rubycas-client and added some enterprisey features and improved compatibility with JASIG's CAS server

Bridge between logig and view

A collections of application helpers.

Allows encryption and signing of requests and storing encrypted data within Mongoid documents.

textile designed for advanced usage, like scheduling versions.

It provides validation of URIs (URLs) to ActiveModel records and ActionControllers in Rails 3.

This toolbox goes in the direction of the django admin interface.

Making your views easier

This gem is intentionally published early. The API is unstable, but the idea is stable. view_component_reducible brings reducer-style (TEA-inspired) state transitions to Rails ViewComponent. Server-driven, HTTP-based, no WebSocket required.

Rails view components

The missing R to the Rails MVC

Description of ViewObject.

Routing filters wraps around the complex beast that the Rails routing system is, allowing for unseen flexibility and power in Rails URL recognition and generation.

Simple, effective A/b testing made easy.

OAuth Core Ruby implementation

Provides webhook handling, background jobs, and data synchronization for the Vindi Rails SDK.

Administrate is heavily inspired by projects like Rails Admin and ActiveAdmin, but aims to provide a better user experience for site admins, and to be easier for developers to customize. To do that, we're following a few simple rules: - No DSLs (domain-specific languages) - Support the simplest use cases, and let the user override defaults with standard tools such as plain Rails controllers and views. - Break up the library into core components and plugins, so each component stays small and easy to maintain.