What problem does it solve?
Redeploying the Dreamverse app on a dev node involves killing stale processes on occupied ports, freeing GPU memory from orphaned workers, exporting the correct environment recipe, and waiting for backend and frontend readiness — a manual sequence that is error-prone and often leads to GPU OOMs from leftover processes.
Core Features & Use Cases
- Automated teardown and relaunch: Kills processes on the target backend/frontend ports and any process holding the target GPU, including orphaned multiproc_executor workers, before booting fresh services.
- Configurable startup modes: Optional GPU warmup, max-autotune torch.compile, and NVENC hardware encoding via flags or environment variables, with readiness budgets scaled to the chosen options.
- Readiness verification: Polls the backend /readyz endpoint and the frontend root until both return 200, then prints URLs, PIDs, and log paths.
- Use Case: After pulling new code for the migrated apps/dreamverse app, run one command to redeploy backend and frontend on GPU 4 with warmup enabled, then run the Playwright e2e suite against the live deployment.
Quick Start
Redeploy the Dreamverse app on GPU 4 with backend port 8009 and frontend port 5299 using the deploy script in this skill.