Add multi client video automation example - #15
Open
musab123-afk wants to merge 2 commits into
Open
Conversation
Companion code for the "A guide to automating video content production for multiple clients" guide: one master template renders branded promos for three clients in three aspect ratios, with a JSON-lines file recording which render belongs to which client. The live article already links this directory.
Derive the API base from SHOTSTACK_ENV (stage default, v1 for
production) instead of hand-editing two files, catch network failures
in status.mjs so they print one line instead of a stack trace, and
widen apiError to the {success, message, response} error shape.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
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
1 participant
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.
Companion code for A guide to automating video content production for multiple clients (https://shotstack.io/learn/automating-video-production-multiple-clients/) — the live article already links this directory, so its GitHub link 404s until this merges. One master template renders branded promos for three clients in three aspect ratios; renders.jsonl records which render belongs to which client, since the API has no endpoint that lists renders.
Gated live twice (including from a fresh clone following the README verbatim): template created, 9/9 submitted, all nine done with URLs. A wrong key prints one-line errors and exits non-zero. Second commit addresses code review: the API base derives from SHOTSTACK_ENV (stage default, v1 for production) instead of hand-editing two files, status.mjs catches network failures with one line instead of a stack trace, and API errors reduce to their message across both response shapes. Prettier passes.