Node.js: Reading environment variables

This documentation is part of the Managing secrets guide. You can view the complete guide here: How to manage secrets with Node.js.

👋 Welcome to the Stackhero documentation!

Stackhero provides a ready-to-use Node.js cloud solution designed to help you move faster:

• Deploy your application to production in seconds with a simple git push. No additional tools or manual configuration required.
• Use your own domain and benefit from automatic HTTPS certificate setup, ensuring your application is secure without any extra steps.
• Enjoy automatic backups, one-click updates, and clear, predictable pricing so you can focus on developing features while Stackhero manages the infrastructure.
• Experience optimal performance and enhanced security thanks to a private, dedicated VM.

Save time and simplify your operations: it only takes a few minutes to try out Stackhero's Node.js cloud hosting solution!

In your app.js file, you can access your environment variable via process.env, like so:

console.log(process.env.MY_PASSWORD);

This will display myDevelopmentPassword.

Your password is now defined outside your code. This helps prevent it from inadvertently ending up in your Git repository.

If you are using Stackhero in production, you can define a new environment variable named MY_PASSWORD with the value myProductionPassword directly from your Node.js service dashboard. This makes it easy to manage different environments smoothly.

Example of Node.js configuration on the Stackhero dashboard

With this approach, your password is no longer stored in your code, and you can easily use different credentials for development and production environments.