Repository navigation
Conversation
Exposes the server's per-bucket media processing profile on the bucket settings page, alongside on-demand migration: a summary row reporting Active / Paused / Not configured, and an editor for the rules that decide which objects are processed and what is produced from them. The editor warns about encoders the server cannot provide. The server drops a rendition whose encoder is missing and the default log level is error, so a profile naming an unavailable codec looks correct and silently derives nothing; naming the missing encoders up front is the difference between a five-second fix and a support ticket. A codec that cannot be carried by the chosen container is rejected before saving, for the same reason: the server would produce a file no browser opens and report nothing. Permissions are gated on the admin:Get/SetBucketMediaProcessing actions the API already requires. Co-Authored-By: Claude Code <noreply@anthropic.com>
Member
|
Why two PR |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Exposes the server's per-bucket media processing profile on the bucket settings page, alongside on-demand migration: a summary row reporting Active / Paused / Not configured, and an editor for the rules that decide which objects are processed and what is produced from them.
The editor warns about encoders the server cannot provide. The server drops a rendition whose encoder is missing and the default log level is error, so a profile naming an unavailable codec looks correct and silently derives nothing; naming the missing encoders up front is the difference between a five-second fix and a support ticket.
A codec that cannot be carried by the chosen container is rejected before saving, for the same reason: the server would produce a file no browser opens and report nothing.
Permissions are gated on the admin:Get/SetBucketMediaProcessing actions the API already requires.
Pull Request
Description
Type of Change
Testing
Checklist
Related Issues
Closes #
Screenshots (if applicable)
Additional Notes