Skip to main content
ProStack uses environment variables for configuration. This guide explains all available variables and their purposes.

Environment Files

ProStack supports multiple environment files:
  • .env: Main environment file for local development
  • .env.docker: Environment variables for Docker deployment
  • .env.production: Production-specific variables (used during build)

Required Environment Variables

These variables are required for the application to function properly:

Authentication Variables

Variables for configuring the authentication system:

AI Chat Variables

Variables for configuring the AI chat feature:

Storage Variables

Variables for configuring file storage: Variables for site verification and social links:

Setting Environment Variables

Local Development

For local development, copy the .env.example file and update the values:
Then update the variables in the .env file with your values.

Docker Deployment

For Docker deployment, use the .env.docker file:
Update the Docker-specific variables like database host.

Production Deployment

For production environments, set environment variables according to your hosting platform:
  • Vercel: Set variables in the Vercel dashboard under “Project Settings > Environment Variables”
  • AWS: Use AWS Parameter Store or Secrets Manager
  • Docker: Use environment variables in your Docker Compose file or Kubernetes secrets
  • PM2: Use environment variables in your PM2 configuration

Securing Environment Variables

Keep your environment variables secure:
  1. Never commit .env files to your repository
  2. Use different values for development and production
  3. Regularly rotate sensitive credentials like API keys
  4. Use secret management tools in production environments

Next Steps

Security

Learn about security best practices

Docker Deployment

Deploy your application with Docker