AliSaZa/admin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
09debac84f
admin/docs/deploy.md
alisaza f9a9afc697 feat: add layout components for various admin dashboard pages 
- Introduced layout components for multiple admin dashboard sections including events, audit logs, bank accounts, blog articles, bookings, chat oversight, cities, contact messages, dashboard, discount codes, event categories, guest lists, identity verifications, manage events, manual notifications, notification rules, payments, provinces, push deliveries, reviews, settlements, sms messages, support tickets, user reports, and users.
- Updated metadata for the auth layout to include the admin page title.
- Modified branch protection documentation to clarify deployment notifications.
2026-09-05 14:29:43 +03:30

713 B
Raw Blame History

Admin deployment

  1. Point the DNS record for backoffice.ghabilee.ir to the production VPS.
  2. Create /opt/ghabilee-admin/.env from .env.example and set production values.
  3. Configure the reverse proxy to forward backoffice.ghabilee.ir to 127.0.0.1:3009 and enable TLS.
  4. Push to main (or run the deploy workflow manually) after the environment is ready.

Deploy Telegram alerts use admin-specific copy in scripts/notify-deploy.sh (success → backoffice URL; distinct from the consumer frontend message).

GitHub secrets checkpoint

Deployment requires VPS_HOST, VPS_USER, and VPS_SSH_KEY. The repository owner will add these GitHub Actions secrets later, before the first deployment.