Operator handover guide
For Deltacomm admins and whoever runs the SMS YANU server.
This guide is for the people who run SMS YANU day to day.
The parts
| Part | Repo | Address |
|---|---|---|
| Accounts, payments, themes | yanu-auth, yanu-auth-ui | auth.smsyanu.com |
| SMS dashboard and HTTP API | yanu-sms | app.smsyanu.com, api.smsyanu.com |
| SMPP gateway (Jasmin) and portal API | yanu-smpp | smpp.smsyanu.com (SMPP port 2775, API under /api/v1) |
| SMPP portal web app | yanu-smpp-portal | smpp.smsyanu.com |
| Docs (this site) | yanu-docs | docs.smsyanu.com |
| Server setup: nginx, compose, backups | yanu-infra | the server |
All services run as Docker containers on one private network (yanu-net), with one shared PostgreSQL server and Redis. The SMPP stack adds the jasmin gateway, its own jasmin-redis, rabbitmq and yanu-smpp-api. Every container is defined in compose/docker-compose.yml in yanu-infra, and the repos live on the server under /opt/yanu/src/.
Daily
- Approve pending top-ups after you check the money arrived.
- Settle any ledger entry in
reconcile("being checked"). See Stuck top-ups. - Look at the Upstream page. It should say connected.
- Glance at reports for a sudden rise in failed messages.
Weekly
- Check backups ran and are a sensible size.
- Look at disk space on the server.
Monthly
- Test a restore from backup.
- Review prices and reseller countries.
- Check TLS certificates are not close to expiry.
Golden rules
- Never edit containers by hand. Change the repo, push to
main, let the deployer pull. - Never put secrets in git or in chat. They live in env files on the server, owned by root, mode
600. - Never credit money you have not seen. Check the bank, mobile money or gateway first.