
Security News
New Website “Is It Really FOSS?” Tracks Transparency in Open Source Distribution Models
A new site reviews software projects to reveal if they’re truly FOSS, making complex licensing and distribution models easy to understand.
Manage encrypted credentials (added in Rails 5.2.0) with multiple environments.
Available as a gem creds
Using Rails command, generate new encrypted file by
bin/rails encrypted:edit config/credentials/production.yml.enc --key config/credentials/production.key
add some content in opened editor (note there is no environment root key, ie no production
):
aws_access_key_id: my-access-key-id
If config/credentials/production.key
doesn't exist yet, run bin/rails generate master_key
and adjust naming to match desired one.
Content of file can be displayed by
bin/rails encrypted:show config/credentials/production.yml.enc --key config/credentials/production.key
Add to config/environments/production.rb
(or any other env)
config.creds = Creds.new("config/credentials/production.yml.enc")
If wants to use key from custom path - by default it checks RAILS_MASTER_KEY
env key and config/master.key
file:
config.creds = Creds.new("config/credentials/production.yml.enc", key_path: "config/credentials/production.key")
In the code:
Rails.configuration.creds.aws_access_key_id
To ease working in development/test environments with the same API, add config/credentials/plain.yml
with key/value pairs
nested under environment name, like:
development:
aws_access_key_id: "aws-key-id"
Then add to config/environments/development.rb
config.creds = Creds.new("config/credentials/plain.yml", env: "development")
In Rails 6.0 it is possible to edit files by rails credentials:edit --environment production
which will look for
config/credentials/production.yml.enc
encrypted by ENV["RAILS_MASTER_KEY"]
or config/credentials/production.key
Rails.configuration.creds.database_url!
config
, like Rails.configuration.creds.config
<%= %>
), but not encrypted onesecret_key_base
is specified in credentials file, it will be assigned to Rails.configuration.secret_key_base
, as it is required by RailsAfter 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/freeletics/creds
The gem is available as open source under the terms of the MIT License.
FAQs
Unknown package
We found that creds 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
A new site reviews software projects to reveal if they’re truly FOSS, making complex licensing and distribution models easy to understand.
Security News
Astral unveils pyx, a Python-native package registry in beta, designed to speed installs, enhance security, and integrate deeply with uv.
Security News
The Latio podcast explores how static and runtime reachability help teams prioritize exploitable vulnerabilities and streamline AppSec workflows.