Hi everyone,
I’m working on a small web project using Ruby on Rails where I want to manage a simple video publishing pipeline with free video editor, and I’m trying to sanity-check the architecture before I scale it further. The idea is:
-
Videos are edited externally in capcut (short-form content, tutorials, social clips)
-
After export, I upload:
-
final MP4 files
-
thumbnails
-
subtitle files (.srt)
-
-
A Rails backend handles:
-
storing metadata (title, duration, tags, publish status)
-
organizing assets per project
-
exposing APIs for a frontend dashboard
-
-
The frontend then serves these videos across a web/app interface
Right now I’m treating capcut purely as the editing layer, and Rails as the system that manages everything after export. What I’m trying to figure out:
-
Is ActiveStorage sufficient for handling capcut video uploads at small-to-medium scale, or should I move media to S3 immediately?
-
Any recommended patterns for versioning edited exports (for example, multiple capcut revisions of the same video)?
-
Would you structure subtitles (.srt) as separate records or attach them directly to video models?
Curious if anyone here has built a similar “video CMS” style system with Rails and external editing tools like capcut.
Would appreciate any feedback on whether this approach is clean or likely to become messy as content volume increases.