How Do I Configure Environment Variables in Shared Hosting?

Introduction

Managing environment variables is essential for running secure and flexible Node.js applications, especially on BigCloudy Node.js hosting, where direct server access is limited. Environment variables let you store sensitive data, like database credentials, API keys, and app settings—outside your code, keeping your application secure and easier to manage across different environments.

In this guide, you’ll learn how to configure and manage environment variables for Node.js applications on BigCloudy using the control panel. We’ll cover how to locate the environment variable settings, add or update variables, and safely access them in your Node.js code. Following these best practices ensures your applications run securely, remain portable across environments, and are ready for production.

Whether you’re deploying a new Node.js app or maintaining an existing project, this article will help you confidently manage environment variables on BigCloudy Node.js Hosting.

What Are Environment Variables?

Environment variables are name-value pairs stored outside your application code that control how your Node.js app runs. They are used for settings that can change between environments (development, staging, production) without changing code.

Common Examples:

NODE_ENV=production → Defines runtime environment.
DB_HOST, DB_USER, DB_PASSWORD → Database credentials.
API_KEY → External service credentials.
PORT → The port number your Node.js app listens on.

Note: Always use environment variables to keep sensitive information out of your code.

Why Use Environment Variables?

Security: Prevents credentials from being hardcoded and exposed in version control.
Flexibility: Easily switch configurations between dev, staging, and production.
Portability: Deploy the same code on multiple servers without modification.
Shared Hosting Compatibility: Control panel provides a safe method to set variables for each app without server-level access.

Setting Environment Variables in Shared Hosting.

Step 1: Open Node.js App Section

Log in to your hosting control panel.
Navigate to Node.js Apps or Application Management.

Step 2: Edit or Create App

Click Edit App or Create New Application.
Locate the Environment Variables section.

Step 3: Add Variables

Enter each variable name and value:
Name: DB_HOST
Value: localhost
Repeat for all required variables.

Note: Use uppercase letters and underscores for readability (e.g., API_KEY).

Step 4: Save and Restart App

Click Apply or Save Changes.
Restart your Node.js application from the control panel to apply variables.

Using Environment Variables in Node.js Apps

Install the dotenv package if your app uses a .env file:

				
					# npm install dotenv

2. Load environment variables in your app.js or server.js:

				
					require('dotenv').config(); 

const port = process.env.PORT || 3000; 
console.log(`Server running on port ${port}`);

For shared hosting, variables set in the control panel override .env values.

Note: Always access variables using process.env.VARIABLE_NAME.

Best Practices

Do not commit .env files with sensitive data to Git.
Validate variables at app startup.
Separate variables per environment (dev, staging, production).
Use descriptive names for variables.
Keep sensitive values secure and avoid exposing them in logs.
Monitor your app after changing variables to ensure they are applied correctly.

Conclusion

Environment variables are the standard method for managing configuration and sensitive values in Node.js applications on shared hosting. The hosting control panel allows these variables to be defined per application without changing source code or requiring elevated access.

After saving variables, restarting the application ensures they are applied correctly. Using clear variable names, keeping credentials out of version control, and separating values by environment helps maintain predictable behavior and reduces configuration errors. This approach keeps Node.js applications secure and manageable within shared hosting limits.

Need Help?

If you require assistance at any point while using this guide, our Support Team is here to help:

Email: support@bigcloudy.com
Submit a support ticket

FAQ

Can I store database passwords in environment variables?

Yes, it is the recommended method for security.

Do environment variables work immediately after saving?

You must restart the app in the control panel to apply changes.

Can I override a .env file with control panel variables?

Yes, control panel variables take precedence over .env files.

What if I need multiple environments?

Create separate Node.js apps for dev/staging/prod or use unique variables per app.

Are there limits on the number of environment variables?

Limits depend on the hosting provider, but typically 20–50 variables are allowed per app.