Fix Docker builds, TS errors, and deploy config
- API: PHP 8.4, composer install --no-scripts + dump-autoload after COPY - Admin: fix TS (Event.upload_password, unused router, api XSRF, window.open) - Upload: Uppy v5 (hideProgressDetails, headers, destroy), unused watch, api XSRF - Build script: loop over api/admin/upload, push :latest as well as VERSION - Deploy: MySQL from docker.io, platform linux/amd64; README troubleshooting Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -43,3 +43,15 @@ After pushing, deploy on the server: set `TAG=1.0.0` in the stack `.env`, then i
|
||||
|
||||
- In Dockge: open the stack → **Pull** (to fetch new images from Gitea) → **Redeploy** (or Stop + Start).
|
||||
- Or on the server: set `TAG=1.0.0` in `.env`, then `docker compose pull && docker compose up -d`.
|
||||
|
||||
## Troubleshooting: "manifest unknown" (e.g. for admin)
|
||||
|
||||
This means the registry has no image for the tag Dockge is using.
|
||||
|
||||
1. **Match the tag** – In the stack `.env`, set `TAG` to the exact tag you pushed (e.g. the git hash from the build output, or `latest`). After running `./scripts/docker-build-push.sh`, the script prints the tag and now also pushes `:latest`, so `TAG=latest` works.
|
||||
2. **Re-push all images** – From project root run `./scripts/docker-build-push.sh` again so api, admin, and upload are all pushed with the same tag.
|
||||
3. **Registry login on the server** – Where Dockge runs, ensure `docker login 10.0.10.205:3000` has been done and that Docker has `10.0.10.205:3000` in `insecure-registries` (if using HTTP).
|
||||
|
||||
### "no matching manifest for linux/amd64" (MySQL)
|
||||
|
||||
The stack pins MySQL to `docker.io/library/mysql:8.0` with `platform: linux/amd64` so the server pulls the correct image from Docker Hub. If your Dockge server is ARM (e.g. Raspberry Pi), change the MySQL service in `docker-compose.yml` to `platform: linux/arm64`.
|
||||
|
||||
Reference in New Issue
Block a user