Skip to main content

​
Environment Variables & Secrets

Securely manage your API keys, tokens, and other sensitive configuration data. Noah provides encrypted storage for all your environment variables, ensuring your secrets never leave your project environment.

​
Identifying Missing Environment Variables

When your dApp requires certain environment variables or API keys, you’ll see a “Missing env variables” warning indicator in your preview. This alerts you that some configuration is needed before your dApp can function properly.
Screenshot showing the missing env variables warning in the preview interface

Missing environment variables warning indicator in the preview

Always configure required environment variables before deploying to ensure your dApp functions correctly in production.

​
Accessing Environment Variables Settings

To manage your environment variables:
1

Open Project Settings

Click the Settings button (gear icon) in your project toolbar to access Project Settings.
Screenshot showing the settings gear icon in the project toolbar

Project settings button location

2

Navigate to Environment Variables

In the Project Settings dialog, click on the “Env. Variables” tab.
Screenshot showing the Env. Variables tab in the project settings interface

Environment Variables tab in project settings

​
Adding Environment Variables

1

Start Adding Variables

Click “Add Variables” to open the environment variable configuration dialog.
Screenshot showing the Add Variables button in the environment variables section

Add Variables button

2

Configure Your Variables

In the dialog, you’ll see fields for: - API_Key: Enter the variable name (automatically prefixed with VITE_REACT_APP_) - Value: Enter the corresponding value (API keys, URLs, configuration strings, etc.)
Screenshot showing the environment variable configuration dialog with key and value fields

Add Environment Variable dialog

You can paste multiple variables at once using KEY=VALUE format, with each pair on a new line.
3

Save Securely

Click Save to encrypt and store your variables securely within the project.
Your environment variables are now encrypted and ready to use in your dApp.

​
Environment Variable Format

All environment variables are automatically prefixed with VITE_REACT_APP_ to ensure they’re accessible in your React application.

​
Example Variables

Common environment variables you might need: 
# API Keys
VITE_REACT_APP_SOLANA_RPC_URL=https://api.mainnet-beta.solana.com
VITE_REACT_APP_COINGECKO_API_KEY=your_coingecko_api_key_here

# Authentication
VITE_REACT_APP_PRIVY_APP_ID=your_privy_app_id
VITE_REACT_APP_WALLET_CONNECT_PROJECT_ID=your_project_id

# Network Configuration
VITE_REACT_APP_NETWORK=mainnet
VITE_REACT_APP_CLUSTER=mainnet-beta

​
Managing Existing Variables

Once you have environment variables configured, you can:
  • View: See all configured variables (values are masked for security)
  • Edit: Update existing variable values
  • Delete: Remove variables you no longer need
  • Add More: Easily add additional variables as your project grows
Screenshot showing the interface for managing existing environment variables

Environment variables management interface

​
Security Features

Encryption

All environment variables are encrypted at rest using industry-standard encryption

No External Storage

Your secrets never leave your project environment - Noah doesn’t store them externally

Masked Values

Variable values are masked in the UI to prevent accidental exposure

Access Control

Only you have access to your project’s environment variables

​
Best Practices

  • Never commit API keys to version control
  • Use descriptive but secure variable names
  • Regularly rotate API keys and update variables
  • Test with development keys before using production credentials
  • Use different variables for development and production environments
  • Group related variables with consistent naming (e.g., SOLANA_, API_) - Document what each variable is used for in your team - Keep a backup of your variable names (not values) for reference - Use environment-specific prefixes when needed
  • Check the “Missing env variables” indicator for configuration issues
  • Verify variable names match what your code expects
  • Ensure all required variables are configured before deployment
  • Test your dApp after adding new variables to confirm they work

​
Next Steps

Protocol Integration

Configure external protocol integrations that use your environment variables

Deploy Your dApp

Once all variables are configured, deploy your dApp with full functionality