# Deploy by Framework

Step-by-step guides to deploy your favorite framework to Wokku. Each guide
takes you from an empty project to a live URL — including the database,
environment variables, and custom domain.

Every guide assumes you have a Wokku account,
a connected server, and an
SSH key registered for git push.

Pick your framework

JavaScript / TypeScript

• Next.js — React, server-rendered or static
• Nuxt — Vue, Nitro server
• Astro — static or SSR
• Node.js / Express — any Node HTTP server

Python

• Django — with migrate + collectstatic
• Flask — Gunicorn
• FastAPI — Uvicorn workers

Other

• Laravel — PHP, with artisan migrate on release
• Ruby on Rails — with migrations + asset precompile
• Go — compiled to a single binary
• Phoenix — Elixir, with Ecto migrations
• Static Site — HTML/CSS/JS or any build output

Don’t see yours? Almost any app deploys the same way: push a repo with a
Procfile (or a Dockerfile) and Wokku builds it. See
Deploy for the generic flow.

How deployment works

Wokku builds your app on your server the moment you git push, using
Cloud Native Buildpacks for most languages (auto-detected
from composer.json, package.json, requirements.txt, go.mod, etc.) or your
own Dockerfile if you provide one. No build config required for the common case.