ruoyi-drama is a Vue 3 front-end for AI short drama creation that talks to a backend ruoyi-ai via Vite proxy. It provides a demo flow from inspiration to storyboard and video synthesis, with instructions for setup, Atlas Key config, and FFmpeg installation.
Collecting history — the radar snapshots this repo daily. The trend line appears after 3 days of data (1 so far).
What it is
The project is a front-end application built with Vue 3, Vite, and Pinia, designed to connect to a backend service ruoyi-ai for AI-assisted short drama creation. It demonstrates a workflow from inspiration input to final video synthesis, including steps for configuration and asset setup.
How it works
The front-end relies on a backend service (ruoyi-ai) to perform the actual AI tasks. It uses a Vite proxy to route API requests to the backend at http://127.0.0.1:6039 by default. Atlas Cloud is used for image/video generation, configured via a Key Config UI that applies a single API key across all Atlas models. The workflow in the UI covers creation center, script polishing, asset configuration, storyboard confirmation, and video synthesis.
Getting started
Install and run the backend first (ruoyi-ai) to ensure the address http://127.0.0.1:6039 is reachable. Then in the frontend:
npm install
npm run dev
If needed, adjust the backend address in .env.development using:
VITE_API_URL=/dev-api
VITE_API_PROXY_TARGET=http://你的后台地址:端口
VITE_CLIENT_ID=后台配置的客户端ID
The default development URL is provided by Vite, and the default backend is http://127.0.0.1:6039.
Recent releases
- none
Traction
- 39 stars, 13 forks (as per repository data)
Behind the repo
- The backend service referenced is ruoyi-ai, with GitHub and Gitee links provided in the README.
Caveats
- License: MIT
- Created: 2026-07-14
- Last push: 2026-07-15
- The README includes specific commands for Atlas Key configuration, and FFmpeg installation steps for Windows via a script, including environment variable handling and required encoders (libx264, aac).
- Production build guidance:
npm run build
The built artifacts are placed in dist/, with a production API prefix of /prod-api by default, and proxying configured to forward to http://127.0.0.1:6039.