You’ll create an app, add your SSH key once, and git push to deploy.
1. Create the app
- Go to Apps → + New app.
- Enter a name, for example
my-app. - Set Resources (CPU and RAM sliders, or a preset). Leave the free size for a hobby app.
- Optionally tick shared add-ons (Postgres, MariaDB, Redis) or pick a dedicated database.
- Click Create App.
wokku apps:create my-app
# with a free shared Postgres and Redis:
wokku apps:create my-app --shared postgres,redis
# with a dedicated database:
wokku apps:create my-app --dedicated-db postgres
Other flags: --branch BRANCH (default main), --dedicated-redis.
The API needs a server_id. Get it from GET /api/v1/servers, then:
curl -X POST https://wokku.cloud/api/v1/apps \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"name": "my-app", "server_id": "SERVER_ID", "deploy_branch": "main"}'
The response includes git_remote and push_instructions.
Ask Claude: “Create an app called my-app with a shared Postgres.”
App names use lowercase letters, numbers and hyphens, and must start with a letter.
2. Add your SSH key (once)
Git pushes are authenticated by your SSH key.
wokku ssh-keys:add --name laptop # uploads ~/.ssh/id_ed25519.pub
Or paste it under Profile → SSH Keys. See SSH Keys.
3. Push your code
git remote add wokku git@git.wokku.cloud:my-app
git push wokku main
The remote and push command are also on the app’s Deploy tab, with copy buttons. When the build finishes, your app is live at https://my-app.wokku.app.
No git? Deploy a local folder instead: wokku deploy:tarball my-app .
How the build works
- If your repo has a
Dockerfileat the root, Wokku builds it. See Deploy with a Dockerfile. - Otherwise Wokku detects your language and builds with Nixpacks.
- Your app must listen on
$PORT. - A
Procfiledefines process types.webgets HTTP traffic; others (likeworker) run only when you scale them. See Background Workers.
During a deploy the new container starts before the old one stops, and crashed containers restart automatically.
Run migrations
There’s no release phase, so a release: line in your Procfile doesn’t run migrations. Run them after the deploy:
wokku run my-app -- bin/rails db:migrate
Check a deploy
wokku deploys my-app # recent deploys
wokku deploys:info my-app DEPLOY_ID # one deploy and its build log
wokku logs my-app --follow # runtime logs
In the dashboard, open the app’s Deploy tab.