🚀 Amba CI/CD Dashboard

Deployment #32

← Back to List
Repository:

AmbaPay/Amba-notification-ms

Branch:

production

Commit:

64f24aad8f243e92dea626ca21820e473d1f1b67

Status:

success

Created At:

1/15/2026, 2:41:21 PM

Commands (8)

git stash save "local changes 2026-01-15T14:41:21.076Z"
Success Exit: 0
Output: 
No local changes to save
git reset --hard HEAD
Success Exit: 0
Output: 
HEAD is now at 12349d6 Merge pull request 'appointment layout change' (#4) from dev into production
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 6 commits.
  (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 12349d6..64f24aa
Fast-forward
 src/services/emailTemplate.service.ts    | 2 +-
 src/templates/email/AppointmentEmail.tsx | 3 +++
 2 files changed, 4 insertions(+), 1 deletion(-)
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

4 vulnerabilities (2 low, 2 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

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   │ 5D     │ 12   │ online    │ 6.7%     │ 149.8mb  │ amba     │ disabled │
│ 0  │ amba_notifications    │ default     │ 1.0.0   │ fork    │ 708610   │ 0s     │ 275  │ online    │ 0%       │ 14.0mb   │ amba     │ disabled │
└────┴───────────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘