admin widget zu dokploy geswitched

docs/queue-supervisor/README.md

@@ -118,14 +118,14 @@ When deploying new code:
 3. Recreate worker/horizon containers: `docker compose up -d --force-recreate queue-worker media-storage-worker horizon`.
 4. Tail logs to confirm workers boot cleanly and start consuming jobs.
 
-### 8. Running inside Coolify
+### 8. Running inside Dokploy
 
-If you host Fotospiel on Coolify:
+If you host Fotospiel on Dokploy:
 
-- Create separate Coolify “services” for each worker type using the same image and command snippets above (`queue-worker.sh default`, `media-storage`, etc.).
+- Create separate Dokploy applications for each worker type using the same image and command snippets above (`queue-worker.sh default`, `media-storage`, etc.).
 - Attach the same environment variables and storage volumes defined for the main app.
-- Use Coolify’s “One-off command” feature to run migrations or `queue:retry`.
-- Expose the Horizon service through Coolify’s HTTP proxy (or keep it internal and access via SSH tunnel).
-- Enable health checks so Coolify restarts workers automatically if they exit unexpectedly.
+- Use Dokploy’s one-off command feature to run migrations or `queue:retry`.
+- Expose the Horizon service through the Dokploy HTTP proxy (or keep it internal and access via SSH tunnel).
+- Enable health checks so Dokploy restarts workers automatically if they exit unexpectedly.
 
-These services can be observed and restarted from Coolify’s dashboard; the upcoming SuperAdmin integration will surface the same metrics/actions through a dedicated Filament widget.
+These services can be observed, redeployed, or reloaded from Dokploy’s dashboard and from the SuperAdmin integration powered by the Dokploy API.