
Security News
Nx npm Packages Compromised in Supply Chain Attack Weaponizing AI CLI Tools
Malicious Nx npm versions stole secrets and wallet info using AI CLI tools; Socket’s AI scanner detected the supply chain attack and flagged the malware.
Add this line to your application's Gemfile:
gem "env_vars"
And then execute:
$ bundle
Or install it yourself as:
$ gem install env_vars
Config = Env::Vars.new do
mandatory :database_url, string
optional :timeout, int, 10
optional :force_ssl, bool, false
optional :rails_env, "development", string, aliases: %w[env]
end
Config.database_url
Config.timeout
Config.force_ssl?
You can specify the description for both mandatory
and optional
methods;
this will be used in exceptions.
Config = Env::Vars.new do
mandatory :missing_var, string, description: "this is important"
end
#=> Env::Vars::MissingEnvironmentVariable: MISSING_VAR (this is important) is not defined
If you're going to use env_vars
as your main configuration object, you can
also set arbitrary properties, like the following:
Config = Env::Vars.new do
optional :redis_url, string, "redis://127.0.0.1"
property :redis, -> { Redis.new } # pass an object that responds to #call
property(:now) { Time.now } # or pass a block.
end
Config.redis.set("key", "value")
Config.redis.get("key")
#=> "value"
Values are cached by default. If you want to dynamically generate new values,
set cache: false
.
Config = Env::Vars.new do
property(:uuid, cache: false) { SecureRandom.uuid }
end
You may want to start a debug session without raising exceptions for missing
variables. In this case, just pass raise_exception: false
instead to log error
messages to $stderr
. This is especially great with Rails' credentials command
(rails credentials:edit
) when already defined the configuration.
Config = Env::Vars.new(raise_exception: false) do
mandatory :database_url, string, description: "the leader database"
end
#=> [ENV_VARS] DATABASE_URL (the leader database) is not defined
I'd like to centralize access to my credentials; there's a handy mechanism for
doing that with env_vars
:
Config = Env::Vars.new do
credential :api_secret_key
credential :slack_oauth_credentials do |creds|
SlackCredentials.new(creds)
end
end
Config.api_secret_key
Config.slack_oauth_credentials
#=> The value stored under `Rails.application.credentials[:api_secret_key]`
You can coerce values to the following types:
string
: Is the default. E.g. optional :name, string
.int
: E.g. optional :timeout, int
.float
: E.g. optional :wait, float
.bigdecimal
: E.g. optional :fee, bigdecimal
.bool
: E.g. optional :force_ssl, bool
. Any of yes
, true
or 1
is
considered as true
. Any other value will be coerced to false
.symbol
: E.g. optional :app_name, symbol
.array
: E.g. optional :chars, array
or optional :numbers, array(int)
. The
environment variable must be something like a,b,c
.json
: E.g. mandatory :keyring, json
. The environment variable must be
parseable by JSON.parse(content)
.If you're using dotenv, you can simply
require env_vars/dotenv
. This will load environment variables from
.env.local.%{environment}
, .env.local
, .env.%{environment}
and .env
files, respectively. You must add dotenv
to your Gemfile
.
require "env_vars/dotenv"
If you want to use env_vars
even on your Rails configuration files like
database.yml
and secrets.yml
, you must load it from config/boot.rb
, right
after setting up Bundler.
ENV["BUNDLE_GEMFILE"] ||= File.expand_path("../../Gemfile", __FILE__)
# Set up gems listed in the Gemfile.
require "bundler/setup"
# Load configuration.
require "env_vars/dotenv"
require File.expand_path("../config", __FILE__)
After checking out the repo, run bin/setup
to install dependencies. Then, run
rake test
to run the tests. You can also run bin/console
for an interactive
prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install
. To
release a new version, update the version number in version.rb
, and then run
bundle exec rake release
, which will create a git tag for the version, push
git commits and tags, and push the .gem
file to
rubygems.org.
Bug reports and pull requests are welcome on GitHub at https://github.com/fnando/env_vars. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
The gem is available as open source under the terms of the MIT License.
Icon made by eucalyp from Flaticon is licensed by Creative Commons BY 3.0.
FAQs
Unknown package
We found that env_vars demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Malicious Nx npm versions stole secrets and wallet info using AI CLI tools; Socket’s AI scanner detected the supply chain attack and flagged the malware.
Security News
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.
Security News
A clarification on our recent research investigating 60 malicious Ruby gems.