7 Commits
Author SHA1 Message Date
efrilmandClaude Opus 5.5 9b21af8892 fix(deploy): require explicit environment and isolate containers per env
Deploying staging from a folder checked out on main replaced the
production container, because the environment was inferred from the
current branch and both environments shared the container name
"apskel-pos".

- Environment is now a required argument (staging|production)
- Refuse to deploy when the branch doesn't match, HEAD is detached,
  or the tree is dirty
- Container name per environment; the legacy "apskel-pos" container
  is only removed by production deploys
- Abort if the port is held by another environment's container
- Confirmation prompt for production (--yes to skip)
- Fast-forward-only pull from origin/<branch>
- Keep the previous image and roll back automatically when the new
  container is not healthy; --rollback for manual rollback

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-30 15:32:25 +07:00
Efril 2b80c92caa feat: deployment 2026-07-09 22:43:01 +07:00
Efril 1533914e4d config: prod and staging 2026-07-09 22:11:03 +07:00
Efril 1a5ddd2b34 update 2026-04-26 23:25:54 +07:00
Aditya Siregar c107733add Update 2025-09-01 16:20:27 +07:00
Aditya Siregar 4c6dc5c8b4 deployment 2025-09-01 16:18:34 +07:00
Aditya Siregar dc23a318cd add deployment 2025-08-08 22:48:57 +07:00