# Deploy a Static Site

Deploy plain HTML/CSS/JS or any build-tool output (Vite, plain SPA, Hugo,
Eleventy) to Wokku.

Prerequisites

• A Wokku account and a connected server
• An SSH key registered for git push
• A folder of static files (or a build that produces one)

1. Create the app

wokku apps:create my-site --server my-server

2. Tell Wokku it’s static

Add an empty Staticfile to the root of what you want served. By default the
repo root is served; set root: if your files live in a subfolder:

# Staticfile
root: public        # omit if files are at the repo root

That’s it — the static buildpack serves your files over HTTP, with clean URLs
and gzip.

3. With a build step (Vite, etc.)

If you build first, use the Node buildpack and serve the output instead:

# package.json
"scripts": { "build": "vite build", "start": "npx serve dist -l $PORT" }

web: npm start

4. Deploy

git remote add wokku git@git.wokku.cloud:my-site
git push wokku main

git remote add wokku git@git.wokku.cloud:my-site
git push wokku main

Live at https://my-site.wokku.app.

Custom domain

Custom Domains — SSL is automatic.

Troubleshooting

• 404s everywhere — check root: in Staticfile points at your files.
• SPA deep links 404 — add a fallback so unknown routes serve index.html (SPA mode).
• Build output not served — with a build step, serve the output dir (dist/build), not the source.

Next steps

• Custom Domains · Logs