How to add environment variables during Node.js application deployment

Add environment variables when deploying your Node.js application on Hostinger

Updated 6 days ago

When deploying a Node.js application on Hostinger, you can configure environment variables as part of the deployment process. Environment variables are commonly used to store sensitive data and configuration values such as database credentials, API keys, and application settings.

During deployment, you have two ways to add environment variables:

  • Import them from a .env file (recommended)

  • Add environment variables manually, one by one

Once all environment variables are added, you can confirm them and continue with building your application.

Before you start

Make sure you know which environment variables your application requires. If using a .env file, ensure it follows the correct format (for example: KEY=value).

Option 1 — Import environment variables from a .env file

Importing variables from a .env file is the fastest option, especially if you already use environment variables locally.

To import from a .env file:

  1. Start the Node.js application deployment process
  2. At the Environment variables step, select Import from .env file

  3. Upload your .env file or paste its contents into the input field

Your .env file should follow this format:

DATABASE_URL=mysql://user:password@host:port/database
API_KEY=your_api_key_here
NODE_ENV=production
  1. Review the imported variables to ensure all required variables are present and there are no typos
  2. Click Confirm to save the environment variables

Option 2 — Add environment variables manually

If you only have a few variables or don’t use a .env file, you can add them manually.

To add environment variables manually:

  1. Start the Node.js application deployment process
  2. At the Environment variables step, click Add

  3. Enter the variable name (for example, DATABASE_URL)
  4. Enter the variable value
  5. Repeat the process for each environment variable
  6. Review the list of environment variables
  7. Click Confirm to save them

NOTES:

  • Environment variables added during deployment are not stored in your repository.
  • If you update environment variables later, you may need to redeploy your application for changes to take effect.
  • Never commit sensitive data such as API keys or passwords directly into your GitHub repository.