Assist_Design/.env.plesk
T. Narantuya 4d0baed4b2 Update Plesk environment configuration and enhance Docker setup
- Added detailed instructions for Plesk deployment in `.env.plesk` and `compose-plesk.yaml`.
- Updated `.gitignore` to exclude Docker-related files.
- Enhanced Dockerfiles for both frontend and backend to optimize for Plesk deployment.
- Refined TypeScript configurations across various files for improved module resolution and compatibility.
- Removed obsolete logger fixes summary file to streamline documentation.
2025-09-01 15:11:42 +09:00

19 lines
801 B
Plaintext

# 🚀 Customer Portal - Plesk Production Environment (Frontend-only sample)
# IMPORTANT: Do NOT store secrets under httpdocs.
# Use split env files in Plesk private path:
# - Frontend (public vars): /var/www/vhosts/asolutions.jp/private/env/portal-frontend.env
# - Backend (secrets) : /var/www/vhosts/asolutions.jp/private/env/portal-backend.env
# See PLESK_DEPLOYMENT.md → Plesk Deployment Notes
# ====== Core ======
NODE_ENV=production
# ====== Frontend (Next.js) ======
NEXT_PUBLIC_APP_NAME=Assist Solutions Portal
NEXT_PUBLIC_APP_VERSION=1.0.0
NEXT_PUBLIC_API_BASE=/api
# For backend/server settings and secrets, move the values to:
# /var/www/vhosts/asolutions.jp/private/env/portal-backend.env
# The backend env should contain DB/Redis URLs, JWT, WHMCS, Salesforce, SendGrid, etc.