rubygems VS dotenv

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.

gem install asciidoctor-pdf ERROR: SSL verification error at depth 2: unable to get local issuer certificate (20) ERROR: You must add /......../=Zscaler Root CA/[email protected] to your local trusted store ERROR: SSL verification error at depth 2: unable to get local issuer certificate (20) ERROR: You must add /......../=Zscaler Root CA/[email protected] to your local trusted store ERROR: SSL verification error at depth 2: unable to get local issuer certificate (20) ERROR: You must add /......../=Zscaler Root CA/[email protected] to your local trusted store ERROR: Could not find a valid gem 'asciidoctor-pdf' (>= 0), here is why: Unable to download data from https://rubygems.org/ - SSL_connect returned=1 errno=0 peeraddr=151.101.1.227:443 state=error: certificate verify failed (unable to get local issuer certificate) (https://rubygems.org/specs.4.8.gz) ERROR: SSL verification error at depth 2: unable to get local issuer certificate (20) ERROR: You must add /......../=Zscaler Root CA/[email protected] to your local trusted store ERROR: SSL verification error at depth 2: unable to get local issuer certificate (20) ERROR: You must add /......../=Zscaler Root CA/[email protected] to your local trusted store

source 'https://rubygems.org' gem 'fibonacci'

# From gemset.nix # actioncable = { dependencies = ["actionpack" "activesupport" "nio4r" "websocket-driver" "zeitwerk"]; groups = ["default"]; platforms = []; source = { remotes = ["https://rubygems.org"]; sha256 = "0ifiz4nd6a34z2n8lpdgvlgwziy2g364b0xzghiqd3inji0cwqp1"; type = "gem"; }; version = "7.1.3.2"; }; ## From Gemfile.lock # actioncable (7.1.3.2) actionpack (= 7.1.3.2) activesupport (= 7.1.3.2) nio4r (~> 2.0) websocket-driver (>= 0.6.1) zeitwerk (~> 2.6)

source 'https://rubygems.org' git_source(:github) do |repo_name| repo_name = "#{repo_name}/#{repo_name}" unless repo_name.include?("/") "https://github.com/#{repo_name}.git" end gem 'pronto' gem 'oj' gem 'pronto-rubocop', require: false gem 'pronto-scss', require: false gem 'pronto-eslint', require: false gem 'pronto-brakeman', require: false gem 'pronto-rails_best_practices', require: false

# Gemfile source "https://rubygems.org" gem 'puppet', '~> 8.4' gem 'onceover', '~> 3.22'

Fetching source index from https://rubygems.org/ Could not verify the SSL certificate for https://rubygems.org/quick/Marshal.4.8/nokogiri-1.13.10-x86_64-linux.gemspec.rz. There is a chance you are experiencing a man-in-the-middle attack, but most likely your system doesn't have the CA certificates needed for verification. For information about OpenSSL certificates, see http://bit.ly/ruby-ssl. To connect without using SSL, edit your Gemfile sources and change 'https' to 'http'

# Gemfile source 'https://rubygems.org' gem 'dotenv' gem 'json' gem 'pry' gem 'rake' gem 'sassc' gem 'sinatra' gem 'sinatra-activerecord' gem 'sinatra-contrib' gem 'sinatra-static-assets' group :development do gem 'foreman' gem 'rubocop' gem 'sqlite3', '~> 1.3', '>= 1.3.11' end group :test do gem 'rack-test' gem 'rspec', require: 'spec' end group :production do gem 'pg' end

I work with Ruby on Rails on a daily basis and use 1Password for password management. In our Rails app we use the dotenv gem and it's always bothered me that we go to all the trouble of being secure, using 1Password with two factor authentication, and yet we have credentials sitting in a text file. Often if any of the credentials are needed by other devs they end up in two places, shared from 1Password and in a .env.local file on their machine.

Note: If you are using dotenv, or you need to add further environment variables this is when. Create your .env.production file and fill it in now.

once ApiConnector is created with configured authorization, you will need to think about It ever again. (always use a secure way to store tokens or other secrets). If you don't know what to use, I can suggest dotenv gem - https://github.com/bkeepers/dotenv

This is the second part of my Test Driving a Rails API series. In Part 1 we set up our development environment, generated a Rails API-only application, installed dotenv to easily store configuration values in the environment, and installed and configured PostgreSQL version 16 as our database.

Storing environment variables for a Rails app can be problematic. The dotenv gem will automatically, when Rails boots, load environment variables from .env files into the Rails ENV. This is a great way to store private information that varies per developer or deployment environment, such as your development database configuration. Rails Encrypted Credentials is a great way to store private information, like API keys, etc, but I wouldn’t use it for storing my local development environment’s database information. The Encrypted Credentials file is checked into the git repository and would, therefore, be shared by all developers on the project. dotenv allows each developer or deployment environment to store their own information in .env files that are ignored by git.

dotenv

Install the dotenv gem.