mattpocock/course-video-manager

Profil mattpocock

Dernière activité source enregistrée: 16 octobre 2026 à 11:35

Catalogue SkillsMP mis à jour: 26 octobre 2026 à 11:37

skills collectés: 9

Étoiles GitHub: 821
Forks GitHub: 170

README du dépôt

Fichier source du README : README.md

Lire le README source

Afficher le README complet

# Course Video Manager A tool for managing course video publishing workflows — editing metadata, generating descriptions, creating thumbnails, and posting to social platforms. ## Repository layout A Turborepo monorepo over the pnpm workspace: | Directory | What it is | | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `apps/local` | The application as it runs on the author's machine: the React Router app, the Video Editor, the Diagram Playground, the Publish flow, ffmpeg, the recorder service, and the `cvm` CLI | | `packages/core` | The domain database — the Drizzle schema, the `DrizzleService` and every `db-*` operations service. Every piece of SQL in the repo lives here | | `packages/overlay-renderer` | The standalone Remotion renderer for every overlay content-kind — subtitles, the CTA, and Definition Cards — with its own toolchain | `packages/core` has **no filesystem access, no `child_process` and no git coupling**, so it can be deployed as well as run locally. `pnpm lint:boundaries` enforces that — anything that needs a machine is injected from `apps/local` (see `packages/core/services/diagram-thumbnail-store.ts` for the shape). `.env` lives at the workspace root: one file for the whole monorepo, which is also where `cvm` looks for it (`apps/local/app/cli/env.ts`). ### Commands Run these from the workspace root; Turborepo fans them out and re-runs only what changed. | Script | Description | | ---------------------- | ------------------------------ | | `pnpm typecheck` | Typecheck every package | | `pnpm test` | Run every suite once | | `pnpm test:watch` | Run every suite in watch mode | | `pnpm lint:boundaries` | Enforce the package boundaries | | `pnpm dev` | Start the local application | | `pnpm build` | Build the local application | Each of these filters out `@cvm/overlay-renderer`: it ships its own toolchain (Remotion, and a Chromium download) and has never been part of the application's checks. Run it with `pnpm --filter @cvm/overlay-renderer`. ### Deploys Vercel gets one project per deployable directory, each with its own Root Directory, and relies on Vercel's **built-in unaffected-project skipping** to decide what to deploy. There is deliberately **no Ignored Build Step**: `turbo-ignore` is deprecated, and native skipping does not consume a concurrent build slot. If a custom step is ever needed it is `turbo query affected`. **Only `main` deploys.** `apps/remote/vercel.json` sets `git.deploymentEnabled` to `{ "**": false, "main": true }`, so a push to any other branch builds nothing: no Preview Deployment for an open PR. Production still deploys on a merge to `main`, because a branch that matches two rules deploys if either one is `true`. The pattern is `**` and not `*`, as `*` does not match a slash and a `feat/thing` branch would still deploy. This is the supported per-branch control — Vercel's dashboard has no equivalent, and the repo takes no Ignored Build Step. ## Database migrations Schema changes are managed with **drizzle-kit generate / migrate** (versioned SQL files), not `push`. The schema, the migrations and the drizzle config all live in `packages/core`. ### Making a schema change 1. Edit `packages/core/db/schema.ts`. 2. `pnpm db:generate` — creates a new numbered `.sql` file under `packages/core/db/migrations/`. 3. Commit it, then `pnpm db:migrate` — run by hand, against `DIRECT_DATABASE_URL` — before or as part of deploying `apps/remote`. Applying migrations used to be the deploy's job exclusively; it moved to a manual step because that ran on every Vercel build, previews included, and could land an unmerged migration on the production schema. See `apps/remote/README.md` and [ADR 0026](docs/adr/0026-migrations-applied-by-hand.md). Against any non-local host, `pnpm db:migrate` (and `drizzle-kit push`) refuses unless you are on a clean `main` at exactly `origin/main` — an unmerged branch once migrated production out of order. Merge first, then migrate from the main checkout. Local databases are never checked. See the ADR 0026 addendum. Migrations are **additive-only**: no dropped or renamed columns without a two-step release. A `cvm` invocation may be in flight while a deploy lands, and it is the additive rule — not the version gate — that keeps that from breaking. The version gate refuses the box's _next_ command, naming both migration counts and telling it to pull (`packages/core/rpc/schema-version.ts`). ### First-time setup on an existing database If the database was originally created via `drizzle-kit push` and has never run migrations: ```sh pnpm db:baseline ``` This registers the `0000` baseline migration as already-applied so the next `pnpm db:migrate` won't replay the initial `CREATE TABLE` statements. ### Scripts | Script | Description | | ------------------ | ------------------------------------------------------------- | | `pnpm db:generate` | Generate a new migration from schema changes | | `pnpm db:migrate` | Apply pending migrations by hand (deploy no longer does this) | | `pnpm db:baseline` | Mark the `0000` baseline as applied (one-time setup) | | `pnpm db:studio` | Open Drizzle Studio | ## Zapier Webhook Setup (Buffer Integration) The app uses a **Dropbox → Zapier → Buffer** pipeline to post videos to social media. When you click "Post to Buffer" in the app, it: 1. Copies the video file into a local Dropbox folder 2. Waits for Dropbox to sync the file to the cloud 3. Sends a webhook to Zapier with the caption and file path 4. Zapier finds the file in Dropbox and adds it to your Buffer queue ### Prerequisites - **Dropbox desktop client** installed and running (the app uses `dropbox filestatus` to poll sync status) - **Buffer account** connected in Zapier - **Zapier account** with access to the Webhooks by Zapier and Buffer integrations ### Environment Variables | Variable | Description | | --------------------------- | -------------------------------------------------------------------------------------------------------------------------------- | | `BUFFER_POSTS_PATH` | Local path to a folder inside your Dropbox directory where video files are copied before posting (e.g. `~/Dropbox/buffer-posts`) | | `ZAPIER_BUFFER_WEBHOOK_URL` | The webhook URL generated by your Zapier Zap (see below) | | `AI_HERO_BASE_URL` | Base URL for the AI Hero instance (e.g. `https://www.aihero.dev`). Required for AI Hero posting integration. | ### Creating the Zapier Zap #### Step 1: Create a "Webhooks by Zapier" trigger 1. Create a new Zap in Zapier 2. For the trigger, choose **Webhooks by Zapier** 3. Select **Catch Hook** as the trigger event 4. Copy the generated webhook URL 5. Set it as the `ZAPIER_BUFFER_WEBHOOK_URL` environment variable in your app The webhook receives a JSON payload with this shape: ```json { "caption": "Your post caption text", "dropboxFilePath": "/full/path/to/buffer-posts/video.mp4" } ``` #### Step 2: Add a "Dropbox: Find File" action 1. Add an action step and choose **Dropbox** 2. Select **Find File** as the action event 3. Configure it to look up the file using the `dropboxFilePath` value from the webhook payload #### Step 3: Add a "Buffer: Add to Queue" action 1. Add another action step and choose **Buffer** 2. Select **Add to Queue** as the action event 3. Map the **media** field to the Dropbox file URL from Step 2 4. Map the **text** field to the `caption` value from the webhook payload #### Step 4: Test and enable 1. Use the app to trigger a test post so Zapier can capture a sample webhook payload 2. Walk through each step to verify the data mapping is correct 3. Turn on the Zap

Chargement du README du dépôt…

Skills dans ce dépôt

Développeurs de logiciels

1 catégories métier · 44% classifié

Installer avec un assistant IA

Copiez ce prompt dans l’assistant IA que vous utilisez.

Follow https://skillsmp.com/skill-install/prompt.md to install Agent Skills from https://github.com/mattpocock/course-video-manager.