Encrypt secret information environment variables by yaml.

EnvCheck is a lightweight Ruby gem that ensures your required and optional environment variables are present and valid before your app boots. Features smart config discovery (.env_check.yml or config/env_check.yml), comprehensive type validation with 9 built-in validators, .env loading with dotenv, and professional CLI tools. Framework-agnostic design works with Rails 7.1+ through Rails 8.0+, Ruby 3.0+.

When you are developing a new feature if your app have some environments like test, staging and production is easy to forget an environment variable in the middle of the process. Also when you migrate the app to another server is easy to forget an environment variable.

Compare ENV variables across Heroku environments

Demonstrates the dangers of using ENV to store credentials

Helpers for dealing with environment variables, with the option of adding the functionality to ENV.

Environmate is a Webhook receiver for various GIT web frontends for deloying Puppet environments to the master/server

Convenience helpers for more simply accessing data passed to applications through the environment that may have types and/or defaults

Load environment variables from .env

A tool for painless parsing and validation of environment variables.

Environment specific paths. A port of node's env-paths

This gem provides Ruby utilities for Env

Shared Rubocop rules for EnvyGeeks

EODData Web Service Client

A wrapper for the Encyclopedia of Life API. It provides simple methods to call all of the available EOL API endpoints.

Ruby client for endoflife.date API

Tools to implement the ePay payment gateway

diff command for EPUB files.

Ephemeron improves the performance of your app. It takes on itself the persistence of the ActiveRecord objects. It protects you from saving the same object many times. It checks whether a fetched from a database object was used. It allows you to eliminate the controller's before_actions that are unnecessarily called. Ephemeron works in the context of the thread and does the bulk of its job (i.a. persistence) at the end of the thread's lifecycle. Although, you can trigger the finalization at any given moment. You don't have to make a distinction in the code for the part that is responsible for the domain logic and the other responsible for the application layers.

Removes recursively nil and empty elements from a hash