Files
MikrotikManager/deploy/updater/targets.json.example
T
Denozordec 7295545cde
Docker images / backend-image (push) Successful in 39s
Docker images / frontend-image (push) Successful in 40s
Docker images / updater-image (push) Successful in 49s
Docker images / notify-webhook (push) Has been skipped
chore: add updater image configuration to Docker workflow
- Introduced a new job for building and pushing an updater Docker image, dynamically setting its name based on the repository structure.
- Updated existing image name configurations for frontend and backend to strip version numbers, ensuring cleaner image tags.
- Enhanced the Docker workflow with steps for checking out the repository, configuring Buildx, and logging into the Gitea registry.
2026-05-12 14:26:59 +07:00

25 lines
565 B
JSON

{
"targets": [
{
"id": "backend",
"container_name": "mmapp-backend",
"image": "git.shts.su/denozord/mikrotikmanager-backend:latest",
"health": {
"type": "http",
"url": "http://127.0.0.1:8000/health",
"expect_status": 200
}
},
{
"id": "frontend",
"container_name": "mmapp-frontend",
"image": "git.shts.su/denozord/mikrotikmanager-frontend:latest",
"health": {
"type": "http",
"url": "http://127.0.0.1:3000/",
"expect_status": 200
}
}
]
}