Mina VS dotenv

After that is ready just run the mina setup command and it will create mina’s folder structure for your project using the parameters you setup before. Read more info on mina setup on their Getting started guide.

However this model is generic to any client-server / monolithic / micro services approach and to any languages and frameworks. In my project I use Mina (Formerly using Capistrano), so that means that on each deployment the script makes a SSH-in to the remote machine and performs the deployment process: Git clone, Git pull, rake db:migrate assets:precompile, puma:restart, etc… Before using Capistrano I was doing all this manually #sigh.

Same with my experience. I could never get Capistrano to work. I blame the never updated documentation that also missing important details here and there so often. Reading the doc is like walking in the woods. In the end I switched to Mina, and finally everything works.

Not to be confused with Mina: blazing fast application deployment tool (https://github.com/mina-deploy/mina)

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.