seperate port and container for external callback

This commit is contained in:
root
2026-08-09 10:24:53 +02:00
parent 3ff0794cfc
commit 639c2b68c8
13 changed files with 155 additions and 16 deletions
+30
View File
@@ -286,3 +286,33 @@ You can verify the active mount with:
```
Images copied directly into `./data/uploads/library` are available in the AssetManager image library after reloading the page.
## Optional dedicated callback port / DMZ listener
AssetManager can expose software-job callbacks through a separate, callback-only Docker service. This is useful when remote devices must send callbacks through an Internet-facing FQDN while the normal AssetManager web interface remains internal.
The optional service exposes only:
- `GET /api/software-callback/health`
- `POST /api/software-jobs/{job_id}/callback`
It does not expose the AssetManager UI, login, assets, settings, static files, or administration routes.
Set the desired host port in `.env`:
```env
CALLBACK_PORT=8090
```
Start the additional service:
```bash
docker compose --profile callback up -d callback
```
The internal callback container listens on port `8001`; Docker maps the configured host port to it. A reverse proxy or firewall can therefore publish only this port/service. For example, a public `https://callback.example.org` can proxy to the Docker host on port `8090`. Configure that public URL under **Software and Jobs → Settings → Callback base URL**.
The standard AssetManager application continues to run on `APP_PORT` (default `8088`). The dedicated callback service is optional; installations that do not enable the `callback` profile behave as before.
For image-based installations, use the same AssetManager image for both the `app` and `callback` services instead of `build: .`. The callback service must always run the same version as the main application.
+1
View File
@@ -1,3 +1,4 @@
- [0.5.5.64](UPDATE-0.5.5.64.md)
- [0.5.5.35](UPDATE-0.5.5.35.md)
- [0.5.5.34](UPDATE-0.5.5.34.md)
# Version history
+10
View File
@@ -0,0 +1,10 @@
# Update 0.5.5.64
## Dedicated callback listener and field-page translations
- Added an optional callback-only Docker Compose service for Internet/DMZ deployments.
- The callback service exposes only the software callback POST route and callback health route; the AssetManager UI is not available on that service.
- Added `CALLBACK_PORT` to `.env.example` with default host port `8090`.
- The optional listener is started with `docker compose --profile callback up -d`.
- The existing callback base URL continues to define the public HTTP/HTTPS FQDN used by job scripts.
- Translated the central field-management page and field editor, including the previously hard-coded **Add field** button and data-type labels.