Who it is forA developer or creator who wants to see the platform running before deciding whether to use it for real content.
The problemSetting up a multi-service AI video platform by hand takes time, and the user needs to know it works before adding API keys.
The outcomeThe user site at localhost:8080, admin at localhost:8081, and API docs at localhost:8000/docs are running, with the health check passing.
What you need first
- Docker Desktop, or Docker Engine with Compose
- A TokenFree API key (sk-...), or set ARK_MOCK=true to try the interface without real generation
- Ports 8000, 8080, and 8081 free on the host machine
Steps
- Clone the repo with
git clone https://github.com/yi1108/printfilm.git, then runcd printfilm. - Create the env file with
cp deploy/.env.docker.example deploy/.env.docker, then set POSTGRES_PASSWORD, SECRET_KEY, and OPENAI_API_KEY / ARK_API_KEY. For a no-key preview, set ARK_MOCK=true. - Start the stack with
docker compose --env-file deploy/.env.docker up -d, then wait about half a minute. - Check the API with
http://localhost:8000/api/healthin a browser or with curl, then open http://localhost:8080 and register at /auth. - Check status with
docker compose --env-file deploy/.env.docker psand read logs withdocker compose --env-file deploy/.env.docker logs -f apiif a service does not start.
Prompt for your agent
In the printfilm repo, copy deploy/.env.docker.example to deploy/.env.docker, set ARK_MOCK=true and strong values for POSTGRES_PASSWORD and SECRET_KEY, then run docker compose --env-file deploy/.env.docker up -d. Output the status from docker compose ps and confirm that http://localhost:8000/api/health responds.
Caveat. The README says the repo has no built-in demo account, so you must register first, and real image or video generation needs a TokenFree key instead of ARK_MOCK=true.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page