
Security News
CISA’s 2025 SBOM Guidance Adds Hashes, Licenses, Tool Metadata, and Context
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.
WIP: This gem is currently under active development. Until 1.0 version backwards-incompatible changes may be introduced with each 0.x minor version.
Configuration and feature management that is pre-loaded into your application at boot-time.
Add this line to your application's Gemfile:
gem 'envoku'
And then execute:
$ bundle install
When Envoku is loaded it automatically uses Dotenv in the background to preload and other configuration mechanisms you may have to make transitioning seamless.
Envoku automatically pre-loads itself during before_configuration
phase so no configuration is required.
Use the plain ruby method as early as possible, before any ENV
variables are accessed. Usually at the top of app.rb
.
Run the following code before you need access to the environment variables
Envoku.load
Feature are defined as standard environment variables as YAML objects in the following format:
ENVOKU_FEATURE_FEATURE1="description: 'Example feature', attribute1: 'something'"
all_features = Envoku::Feature.all
feature = Envoku::Feature.new('FEATURE1')
feature.enabled? # global for all resources
feature.enabled_for?(current_user) # does current_user have this feature enabled
feature.enable_for!(current_user) # enable feature for current_user
feature.disable_for!(current_user) # disable feature for current_user
feature.attributes # {"attribute1" => "something"}
feature.permitted_for?('User') # whether or not this feature is designed for a resource
resource.feature_enabled?('FEATURE1')
resource.toggle_feature!('FEATURE1')
resource.features_enabled
By default, all features can be used against all resources. To restrict a feature to a certain resource:
ENVOKU_FEATURE_FEATURE1="permitted_resources: 'Organization,User'"
Per-resource features are stored in Redis via the following keys:
(SET) envoku:features:[feature]:[class] 123 456 789 # IDs for resource grouped by feature and class
(SET) envoku:features:[class]:[id] FEATURE1 FEATURE2 # Features grouped by resource and ID
Envoku.configure {}
functionalityAfter checking out the repo, run bin/setup
to install dependencies. Then, run rake spec
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/marcqualie/envoku-ruby.
FAQs
Unknown package
We found that envoku 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
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.
Security News
ESLint now supports parallel linting with a new --concurrency flag, delivering major speed gains and closing a 10-year-old feature request.