fastify-passport VS dotenv

Passport.js isn't limited to just Express, you can use our strategy with other frameworks with Passport compatibility like NestJS, Fastify, or Koa.

Downside: middleware like passport.js might not work with fastify, you will have to spend some time to make it work. For passport there is a wrapper, and I don't know other useful express middlewares.

Today we're going to be discussing the easiest way to integrate Dotenvx into a project that heavily utilizes Docker services. Dotenvx is an open-source environment variable management tool that specializes in handling secrets and was created by the developer of the popular tool Dotenv. Dotenvx serves as the successor to Dotenv.

As a backend developer, I've been working with typescript, on some projects we are required to use different types of environment files, the most common is using environment files, but there are some specific cases where we need to use other types because the tools that we use requires a yaml, JSON or other file formats, we already have a perfect tool like dotenv-yaml - npm or dotenv - npm. But something comes to my mind, what if we have a package that can support any env files 🤔...

Dotenv: For loading environmental variables.

We will put our Emailjs environment variables in a dotenv (.env) file. To read more about the purpose of this file click here.

Add .env to your .gitignore file to prevent it from being committed. Here's an example file with it already added. You may also use dotenv for advanced configuration and it will automatically load environment variables from a .env file into process.env.

dotenv: Designed to load environment variables from a .env file into the process.env environment

Like Doppler, Infisical uses environment variable injection. Similar to the Dotenv package for Node, when used in Node, it injects them at run time into the process object of the running app so they're not readable by any other processes or users. They can still be revealed by a crash dump or logging, so that is a caveat to consider in your code and build scripts.

We'll be working with databases' ids and different info that should be secured so I would advise you to create a .env file to store said info. We'll do this by installing dotenv into our project and use it accordingly:

dotenv - For reading our API keys from the environment