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 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!

Initially, 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 believe 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 nobody notices. This can eventually lead to serious security issues.

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