Node.js: What you might be tempted to do

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 offers a ready-to-use Node.js cloud solution designed to help you move faster:

• Deploy to production in seconds with a simple git push. No additional tools or manual configuration needed.
• Use your own domain and take advantage of automatic HTTPS certificate setup, keeping your application secure with no extra steps.
• Enjoy automatic backups, one-click updates, and predictable, transparent pricing so you can focus on building features while Stackhero manages the infrastructure.
• Benefit from dedicated, private infrastructure for optimal performance and enhanced security.

Save time and simplify your operations: you can have your application running on Stackhero's Node.js cloud hosting in just a few minutes.

At first, you might consider writing your credentials directly in your code, like this:

// Connecting to a PostgreSQL database
const pg = new Client({
  host: '<XXXXXX>.stackhero-network.com',
  user: 'admin',
  password: 'myPassword',
  database: 'admin'
});

However, this method is not secure. Your secrets could end up in your Git repository, making them accessible to anyone with access to the code. Even if you think you are the only one with access, it is a bit like leaving a Post-it note with your passwords on your monitor and hoping no one notices. This can eventually lead to serious security issues.

Additionally, hard-coding secrets makes it difficult to manage different environments, such as development and production.