retire openreel fork after in-house editor stabilizes #9

New issue

Closed

opened 2026-05-18 10:27:54 -04:00 by zgaetano · 0 comments

zgaetano commented

2026-05-18 10:27:54 -04:00

Owner

When the in-house editor (edit.html + js/edit.js + Phase B/C issues) is feature-complete and battle-tested:

Remove services/editor from docker-compose.yml
Drop the openreel route (port 47435) from nginx
Remove the openreel asset-import bridge code (services/editor/apps/web/src/mam-bridge.ts)
git rm -r services/editor

Don't do this until Phase C export is done and we've run a real edit through it. Until then the openreel fork stays running as a fallback.

When the in-house editor (`edit.html` + `js/edit.js` + Phase B/C issues) is feature-complete and battle-tested: - Remove `services/editor` from `docker-compose.yml` - Drop the openreel route (port 47435) from nginx - Remove the openreel asset-import bridge code (`services/editor/apps/web/src/mam-bridge.ts`) - `git rm -r services/editor` Don't do this until Phase C export is done and we've run a real edit through it. Until then the openreel fork stays running as a fallback.