Mvox / RS Milow Audio — Ops Guide

3.1 — Deploy the website

Every site file change (pricing, copy, layout, new pages) needs this to go live. Claude can edit every file but is blocked from running this specific command — it'll hand you the exact line to paste.

Set-Location "C:\Users\Rohit\Desktop\Mvox Website"
$token = (Get-Content .env | Where-Object { $_ -match '^VERCEL_TOKEN=' }) -replace '^VERCEL_TOKEN=', ''
npx.cmd vercel --prod --yes --token $token

3.2 — Push a new plugin build live

Two ways, depending on scale:

1. One file: sign in to your personal account, go to Account → Upload Installers, and drag the new build onto the matching slot. It replaces the file on GitHub instantly — no site redeploy, nothing else to do.
2. A whole batch (e.g. after a source change that touches every plugin): rebuild everything, copy the fresh installers into Mvox Website\downloads\, then run:

   cd "C:\Users\Rohit\Desktop\Mvox Website"
   node scripts/seed-github-releases.js

   This uploads every file in that folder to the release, replacing whatever's already there under the same name.

3.3 — Change a price

Stripe prices can't be edited once created — changing one always means creating a new Price object and retiring the old one. This touches four places, every time:

1. Stripe: create the new Price on the same Product, set it as the product's default, deactivate the old Price (don't delete it — old receipts still point to it)
2. supabase/functions/create-checkout-session/index.ts — the price ID map and the base-price map used for the launch-sale math and the suite-upgrade credit
3. supabase/functions/admin-api/index.ts — the price used for revenue reporting
4. account/dashboard.html and index.html — the displayed number in two homepage spots plus the dashboard's locked-product tag

Just tell Claude the new number — it knows this whole chain and updates all four in one pass.

3.4 — Change the database

supabase db push is broken for this project (its migration history got out of sync early on). Every schema change instead goes through Supabase's Management API directly: a new numbered file in supabase/migrations/, applied as a raw SQL call. Claude has this workflow memorized.

3.5 — Update backend logic (an Edge Function)

Unlike the site, Claude can run this one directly:

cd "C:\Users\Rohit\Desktop\Mvox Website"
npx supabase functions deploy <function-name>

Takes effect immediately, live, no further steps.

3.6 — Rebuild the plugin (Windows)

1. Build: open a Developer Command Prompt (or run vcvarsall.bat x64 first), cd into Mvox\build, run cmake --build . — the project's generator is Ninja (single-config), so the build type comes from the cached CMAKE_BUILD_TYPE value, not a --config flag on this command (that flag is a Visual-Studio-generator thing and is silently ignored here)
2. Only the main Mvox target auto-copies itself into C:\Program Files\Common Files\VST3\ after building. The 9 mini-plugins don't — copy each one's .vst3 folder over manually every time
3. To cut new installers: stage the fresh .vst3 folders into Desktop\mvox parts\, run BuildMiniInstallers.ps1 (the 9 minis) and the two ISCC.exe MvoxSuite...Installer.iss commands (suite + trial)

3.7 — Change which Discord role gets pinged

There's no bot, only a webhook, so this can't be changed from Discord's side — the role ID is hardcoded into two Postgres trigger functions. Get the new role's ID (Discord → enable Developer Mode → right-click the role → Copy Role ID) and hand it to Claude.