🚀 Amba CI/CD Dashboard

Deployment #24

← Back to List
Repository:

AmbaPay/Amba-notification-ms

Branch:

production

Commit:

2c72fe024e8e5c100ec4b6bcb971dc75df373e60

Status:

success

Created At:

1/10/2026, 7:26:34 PM

Commands (8)

git stash save "local changes 2026-01-10T19:26:34.905Z"
Success Exit: 0
Output:
No local changes to save
git reset --hard HEAD
Success Exit: 0
Output:
HEAD is now at 3063173 Empty commit to trigger CI/CD - 3
git fetch https://***:***@gitea.yaltopia.com/AmbaPay/Amba-notification-ms.git production
Success Exit: 0
Error:
fatal: unable to bind to '/home/amba/.cache/git/credential/socket': Read-only file system
warning: unable to unlink '/home/amba/.cache/git/credential/socket': Read-only file system
fatal: cache daemon did not start: 
From https://gitea.yaltopia.com/AmbaPay/Amba-notification-ms
 * branch            production -> FETCH_HEAD
git checkout production
Success Exit: 0
Output:
Your branch is ahead of 'origin/production' by 1 commit.
  (use "git push" to publish your local commits)
Error:
Already on 'production'
git pull https://***:***@gitea.yaltopia.com/AmbaPay/Amba-notification-ms.git production
Success Exit: 0
Output:
Updating 3063173..2c72fe0
Fast-forward
 src/services/emailTemplate.service.ts    | 11 ++++
 src/templates/email/AppointmentEmail.tsx | 93 ++++++++++++++++++++++++++++++++
 2 files changed, 104 insertions(+)
 create mode 100644 src/templates/email/AppointmentEmail.tsx
Error:
fatal: unable to bind to '/home/amba/.cache/git/credential/socket': Read-only file system
warning: unable to unlink '/home/amba/.cache/git/credential/socket': Read-only file system
fatal: cache daemon did not start: 
From https://gitea.yaltopia.com/AmbaPay/Amba-notification-ms
 * branch            production -> FETCH_HEAD
npm install --include=dev
Success Exit: 0
Output:
up to date, audited 438 packages in 2s

60 packages are looking for funding
  run `npm fund` for details

2 high severity vulnerabilities

To address all issues, run:
  npm audit fix

Run `npm audit` for details.
Error:
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@react-email/code-block@0.2.0',
npm WARN EBADENGINE   required: { node: '>=22.0.0' },
npm WARN EBADENGINE   current: { node: 'v20.19.2', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@react-email/markdown@0.0.17',
npm WARN EBADENGINE   required: { node: '>=22.0.0' },
npm WARN EBADENGINE   current: { node: 'v20.19.2', npm: '9.2.0' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@react-email/render@2.0.0',
npm WARN EBADENGINE   required: { node: '>=22.0.0' },
npm WARN EBADENGINE   current: { node: 'v20.19.2', npm: '9.2.0' }
npm WARN EBADENGINE }
npm run build
Success Exit: 0
Output:
> notification-service@1.0.0 build
> tsc

pm2 restart /home/amba/amba_services/pm2_services/ecosystem.config.js --only amba_notifications
Success Exit: 0
Output:
[PM2] Applying action restartProcessId on app [amba_notifications](ids: [ 0 ])
[PM2] [amba_notifications](0) ✓
┌────┬───────────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name                  │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├────┼───────────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 1  │ amba_events           │ default     │ 1.0.0   │ fork    │ 593213   │ 8h     │ 12   │ online    │ 0%       │ 144.2mb  │ amba     │ disabled │
│ 0  │ amba_notifications    │ default     │ 1.0.0   │ fork    │ 601073   │ 0s     │ 273  │ online    │ 0%       │ 15.7mb   │ amba     │ disabled │
└────┴───────────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘