Guides | Kuppit Docs

Guides

Walkthroughs from a repository to a running application, one per framework, and for the things you do after the first deployment.

Each guide takes one kind of application from a repository to a live URL on Kuppit, and says what that framework needs to know about PORT, its build, and the values it reads at runtime. They assume the Quickstart, which is the same walk for a repository Kuppit detects on its own.

Deploy a framework

Nuxt

Detected from the nuxt dependency. Nitro reads PORT itself; runtime config comes from NUXT_ variables.

Next.js

Detected from the next dependency. next start reads PORT; public values are inlined at build time, which changes where they live.

Express

Detected from the express dependency and a start script. Your server must listen on PORT and 0.0.0.0.

A Dockerfile

Any language. Kuppit builds the Dockerfile as written and routes to port 8080.

After the first deployment

Create a staging environment: a long-lived copy of Production on its own branch, deciding per resource what it gets.

Was this page helpful?

Deleting an environment

What goes, what survives, and why Kuppit sometimes refuses.

Deploy a Nuxt application

From a Nuxt repository to a live URL, with runtime config from variables and a database behind it.