.env.example

# ============================================
# VertexChain Root Environment Configuration
# ============================================
#
# This file documents shared environment variables used across multiple workspaces.
# Each workspace (Backend, Frontend, Analytics) has its own .env.example file
# with workspace-specific configuration.
#
# Please refer to the individual workspace .env.example files:
# - Backend/.env.example    - API server configuration
# - Frontend/.env.example   - Main frontend application
# - analytics/.env.example  - Analytics dashboard
#
# ============================================
# Shared Configuration
# ============================================

# NODE_ENV (optional)
# Application environment mode used across all Node.js workspaces
# Values: development | production | test
# Default: development
NODE_ENV=development

# ============================================
# Setup Instructions
# ============================================
#
# 1. Make sure you have Node.js 20 installed (use nvm: `nvm use`)
# 2. Copy this file and workspace-specific .env.example files to .env:
#    - cp Backend/.env.example Backend/.env
#    - cp Frontend/.env.example Frontend/.env
#    - cp analytics/.env.example analytics/.env
# 3. Update each .env file with your actual configuration values
# 4. Install dependencies in each workspace:
#    - cd Backend && npm install
#    - cd Frontend && npm install
#    - cd analytics && npm install
# 5. Start the development servers (see CONTRIBUTING.md for details)
#
# ============================================
# Quick Reference - Required Services
# ============================================
#
# Backend requires:
# - PostgreSQL database (local or remote)
# - Stellar/Soroban RPC endpoint (testnet/mainnet)
# - (Optional) Pinata account for IPFS pinning
#
# Frontend requires:
# - Backend API server running
#
# Analytics requires:
# - Mapbox account and access token
# - (Optional) Backend API server for live data
#