🚀 Amba CI/CD Dashboard

Deployment #1

← Back to List
Repository:

AmbaPay/Amba-events

Branch:

production

Commit:

N/A

Status:

success

Created At:

12/26/2025, 8:01:34 AM

Commands (12)

git config --get remote.origin.url
Success Exit: 0
Output: 
https://gitea.yaltopia.com/AmbaPay/Amba-events.git
git remote set-url origin https://***:***@gitea.yaltopia.com/AmbaPay/Amba-events.git
Success Exit: 0
git stash save "local changes 2025-12-26T08:01:34.653Z"
Success Exit: 0
Output: 
No local changes to save
git reset --hard HEAD
Success Exit: 0
Output: 
HEAD is now at a13e86e ts build issues fix
git fetch origin 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-events
 * branch            production -> FETCH_HEAD
 * [new branch]      production -> origin/production
git checkout production
Success Exit: 0
Output: 
branch 'production' set up to track 'origin/production'.
Error: 
Switched to a new branch 'production'
git rev-parse HEAD
Success Exit: 0
Output: 
5607ed02de2aa2cad355c8ee241ac5b6989c5341
git pull origin production
Success Exit: 0
Output: 
Already up to date.
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-events
 * branch            production -> FETCH_HEAD
git rev-parse HEAD
Success Exit: 0
Output: 
5607ed02de2aa2cad355c8ee241ac5b6989c5341
npm install --include=dev
Success Exit: 0
Output: 
up to date, audited 590 packages in 2s

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

14 vulnerabilities (4 low, 1 moderate, 7 high, 2 critical)

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

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
npm run build
Success Exit: 0
Output: 
> event-management-be@1.0.0 build
> tsc
pm2 restart /home/amba/amba_services/pm2_services/ecosystem.config.js --only amba_events
Success Exit: 0
Output: 
[PM2] Applying action restartProcessId on app [amba_events](ids: [ 1 ])
[PM2] [amba_events](1) ✓
┌────┬───────────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name                  │ namespace   │ version │ mode    │ pid      │ uptime │ ↺    │ status    │ cpu      │ mem      │ user     │ watching │
├────┼───────────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 1  │ amba_events           │ default     │ 1.0.0   │ fork    │ 238451   │ 0s     │ 3    │ online    │ 0%       │ 5.6mb    │ amba     │ disabled │
│ 0  │ amba_notifications    │ default     │ 1.0.0   │ fork    │ 195188   │ 42h    │ 5    │ online    │ 0%       │ 91.3mb   │ amba     │ disabled │
└────┴───────────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘