Add bulk gallery management and direct organizer uploads
This commit is contained in:
@@ -81,3 +81,8 @@ unhealthy. Long exports can exceed this threshold and should be investigated.
|
||||
Checks run every 30 seconds, with a 5-second timeout and three retries. No worker
|
||||
health port is published. Docker health status by itself does not automatically
|
||||
restart an unhealthy container; it supplies readiness information to Coolify.
|
||||
# Bulk gallery workflows
|
||||
|
||||
Use `manager_photos` with `input.limit`, `input.offset`, optional `input.visibility` and `input.processingStatus` to inspect a page. Capture explicit photo IDs; a bulk request never expands to later uploads. `manager_previewBulkPhotos` checks up to 100 IDs for an action (`public`, `hidden`, `private`, `rejected`, `delete`). Pass eligible IDs to `manager_bulkPhotos` with both `input.confirm=true` and the MCP write wrapper's `confirm=true`. Results are per photo, including skipped/failed items. Permissions are rechecked during execution. Deletion skips photos still uploading or processing, permanently removes originals and variants, and can partially succeed; inspect results before retrying.
|
||||
|
||||
For organizer uploads, `manager_createGalleryPhotos` accepts up to 25 file descriptors and returns presigned PUT URLs in input order. PUT each original directly to storage with its matching Content-Type, then call `manager_completeGalleryPhotos` with successful IDs to validate size and queue transcoding. These actions require existing `settings.manage` permission. Photos start pending review, even when guest publication is automatic. Do not blindly retry creation: it creates a new batch. No file bytes pass through MCP or Next.js.
|
||||
|
||||
Reference in New Issue
Block a user