100-days-of-code VS dotenv

Thinking about doing the #100DaysOfCode Challenge on X/Twitter? Well, you've come to the right place!

#100DaysOfCode Official Website | #100DaysOfCode

100 Days of Code Challenge is an initiative I am commiting to take, where I will be spending each day working on problem solving and personal projects to improve my skills and push my boundaries.

I'm participating in the #100DaysOfOSS challenge by OpenSauced. Inspired by the #100DaysOfCode challenge, #100DaysOfOSS is a challenge for everyone interested in open source to learn about open source, contribute, or maintain open source projects over 100 days, starting on July 24th.

Inspired by the great work of the #100DaysOfCode challenge, we're launching #100DaysOfOSS, starting July 23rd, and running through the end of Hacktoberfest, October 31.

When I started to learn Python, I joined #100DaysOfCode challenge on Twitter. Strangers supported me under my daily tweets and this helped me build a daily habit of coding. If I do something hard, I will need someone who cares and will cheer me up. It’s more important than it seems.

Here is the official site: https://www.100daysofcode.com/

So you're should be thinking: why I entered on the #100daysofcode challenge? Very simple: I'm a newbie in a lot of technologies and concepts. I focused all this time to learn PHP and Laravel, Linux and other stuffs to get a job and enter the market but now I have a new challenge to move on.

There's also -- https://www.100daysofcode.com/ -- I haven't explored their resources or curriculum tbh, but they seem to understand the importance of community.

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

As an avid dotenv user I wanted to thank their maintainers for keeping the project alive for 10 years (wow). A perfect exemplary of dedication to Open Source.

Sensitive data like database URLs, API keys, and passwords should never be hardcoded in your application code. Instead, use environment variables accessed at runtime to keep this information secret. Popular dotenv libraries like dotenv make this easy for Node.js apps.