Guilan ACE Deployment

Local and deployment layout

parent-directory/
  guilan-ace-backend/
  guilan-ace-frontend/
  guilan-ace-deployment/
    backend/
      Dockerfile
    frontend/
      Dockerfile
    certs/
    traefik/
    docker-compose.yml
    grafana-datasources.yml
    nginx-static.conf
    prometheus.yml

Usage

1. Keep guilan-ace-backend, guilan-ace-frontend, and guilan-ace-deployment as sibling repositories in your local workspace.
2. Copy .env.example to .env.
3. On the deployment server, place the backend repo at guilan-ace-deployment/backend/guilan-ace-backend.
4. On the deployment server, place the frontend repo at guilan-ace-deployment/frontend/guilan-ace-frontend.
5. Create backend/guilan-ace-backend/.env from the backend repo sample.
6. Create frontend/guilan-ace-frontend/.env from the frontend repo sample.
7. Run docker compose up -d --build.

Notes

• Traefik terminates TLS and routes frontend, API, admin, static, media, Grafana, Prometheus, and Uptime Kuma.
• The frontend is a Next.js standalone Node runtime behind Traefik on internal port 3000.
• Alertmanager has been removed from this stack. Prometheus scraping and Grafana provisioning remain intact.
• Dockerfiles live only in this deployment repository, and compose is intentionally wired only for the nested production layout.