secret-token
dotenv
| secret-token | dotenv | |
|---|---|---|
| 1 | 20 | |
| 2 | 6,514 | |
| - | - | |
| 0.0 | 8.6 | |
| about 3 years ago | 4 days ago | |
| Python | Ruby | |
| Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
secret-token
-
RFC 8959: The “secret-token” URI Scheme
This is a neat idea. I've thrown together a small Python library for working with these: https://github.com/Lexicality/secret-token
dotenv
-
Test Driving a Rails API - Part Two
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.
-
Test Driving a Rails API - Part One
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.
-
Performance e elegância! Escrevendo uma CLI CRUD utilizando ScyllaDB e Ruby
dotenv
- Samhlaigh na féidearthachtaí!
- We have this many ".env" files in a project at work. Is this normal? Is there a better way?
-
Bootstrapping with Ruby on Rails Generators and Templates
Install the dotenv gem.
- Dum: An NPM scripts runner written in Rust
- railstart-niceadmin support more features
-
railstart-niceadmin release now!Backend management system based on Bootstrap 5 and NiceAdmin and Rails 7
dotenv-rails
-
Where Rails look for environment variables
Yeah, now that I think of it, it does require a gem. I have used this in most projects https://github.com/bkeepers/dotenv
What are some alternatives?
detect-secrets - An enterprise friendly way of detecting and preventing secrets in code.
Figaro - Simple Rails app configuration
lockgit - A CLI tool for storing encrypted data in a git repo
RailsConfig - Easiest way to add multi-environment yaml settings to Rails, Sinatra, Padrino and other Ruby projects.
cross-env
ENVied - Ensures presence and type of your app's ENV-variables (mirror)
Configatron - A super cool, simple, and feature rich configuration system for Ruby apps.
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
hardhat-deploy - hardhat deployment plugin
Global - "Global" provides accessor methods for your configuration data
Mongoose - MongoDB object modeling designed to work in an asynchronous environment.
fastify - Fast and low overhead web framework, for Node.js