fix: use NAS-local Gitea registry for CRM
Some checks failed
Build & Push Monica Image to Gitea Registry / build-and-push (push) Failing after 7s

This commit is contained in:
Kroonk
2026-05-22 16:53:06 +02:00
parent 0932a84a2b
commit 8195bb8ccf
3 changed files with 9 additions and 13 deletions

View File

@@ -6,13 +6,14 @@ This repository is the MischLabs fork of Monica CRM, based on the upstream `moni
- Gitea repository: `https://git.mischlabs.de/MrDiderot/CRM.git`
- Upstream base: `https://github.com/monicahq/monica`, branch `4.x`
- Registry image: `git.mischlabs.de/mrdiderot/crm:latest`
- NAS-internal registry image: `localhost:3001/mrdiderot/crm:latest`
- Public Gitea package UI: `https://git.mischlabs.de/MrDiderot/-/packages/container/crm/latest`
- NAS path: `/volume2/docker/mischcrm`
- Default NAS port: `38090:80`
## Architecture
The NAS does not build the image locally. Gitea Actions builds the Monica image from `scripts/docker/Dockerfile` and pushes it to the local Gitea registry. The NAS runs:
The NAS does not build the image locally. Gitea Actions builds a MischLabs package image from the official Monica Apache image and pushes it to the local Gitea registry through `localhost:3001`. This avoids Cloudflare upload limits for large Docker layers. The NAS runs:
- `mischcrm`: Monica Apache web container
- `mischcrm_cron`: Monica scheduler container using `cron.sh`
@@ -59,7 +60,7 @@ docker logs mischcrm --tail=120
## Updates
Watchtower should update `git.mischlabs.de/mrdiderot/crm:latest` automatically after Gitea Actions pushes a new image.
Watchtower should update `localhost:3001/mrdiderot/crm:latest` automatically after Gitea Actions pushes a new image.
Manual update:
@@ -76,7 +77,7 @@ Do not commit `.env`.
Do not delete the Docker volumes unless you explicitly want to remove Monica data.
If Monica redirects incorrectly behind Cloudflare/Nginx Proxy Manager, check:
If Monica redirects incorrectly behind Cloudflare, check:
- `APP_URL`
- `APP_TRUSTED_PROXIES=*`