Deploy a Bun application

​

At a glance

​

Environment variables

​

Before you begin

• A Sevalla company with a payment method, and a GitHub, GitLab or Bitbucket account for the repository. See Git providers.
• Bun 1.4 or later on your computer.

​

Create the project

mkdir storefront && cd storefront
bun init -y

const server = Bun.serve({
  routes: {
    "/": new Response("Hello from Bun on Sevalla"),
  },
  fetch() {
    return new Response("Not Found", { status: 404 });
  },
});

console.log(`Listening on ${server.url}`);

process.on("SIGTERM", async () => {
  console.log("SIGTERM received, stopping the server");
  await server.stop();
});

​

Prepare the project for Sevalla

bun pm pkg set engines.bun="1.x"

• It detects Bun from bun.lock, which bun init wrote, installs Bun and runs bun install --frozen-lockfile. Commit bun.lock: without it, Ingot builds the project with npm and Node.js, and the build fails with No start command found.
• It takes the Bun version from engines.bun: 1.x follows the newest Bun 1 release, so each build gets its fixes. Without engines.bun, Ingot uses its default Bun line, which a new Ingot release can move.
• It starts the web process with bun index.ts, the file in the module field that bun init set. A start script in package.json replaces it.
• Bun runs TypeScript directly, so the project needs no build step. Ingot removes the devDependencies, such as @types/bun, after the install.

git init
git add .
git commit -m "Prepare for Sevalla"
git branch -M main
git remote add origin https://github.com/acme/storefront.git
git push -u origin main

​

Deploy to Sevalla

​

Verify the deployment

1. On the Deployments tab, click the deployment. Its Build log shows Ingot’s build plan: Bun 1 and the Bun 1.x package manager for the "1.x" in engines.bun, and bun index.ts, from the module field, as the start command. Ingot builds Bun applications on its Node.js image and adds Bun to it, so the plan also names Node.js.
   Build log

   ╭─ ■ Node.js 24 application ────────────────────────────────╮
   │ Node.js          24            default                    │
   │ Bun              1             package.json engines "1.x" │
   │ Package manager  bun 1.x       package.json engines       │
   │ Start            bun index.ts  package.json module        │
   │ DevDependencies  removed after the build                  │
   ├─ Image ───────────────────────────────────────────────────┤
   │ Build            node:24-trixie                           │
   │ Runtime          node:24-trixie-slim                      │
   │ User             1000:1000                                │
   │ Init             tini                                     │
   │ Port             $PORT, default 8080                      │
   ╰──────────────────────────────────────────── Ingot v0.5.0 ─╯
   
2. Wait for the deployment’s status to change to Deployed. The application’s status next to its name changes to Running.
3. Click the domain under the application’s name, for example storefront-x7k2m.sevalla.app. The page shows Hello from Bun on Sevalla.
4. Check the same address from a terminal:
   curl -s https://storefront-x7k2m.sevalla.app/
   
   Hello from Bun on Sevalla
   

​

Deploy with a Dockerfile

FROM oven/bun:1-slim
WORKDIR /app
ENV NODE_ENV=production PORT=8080
COPY package.json bun.lock ./
RUN bun install --frozen-lockfile --production --omit=peer && bun pm cache rm
COPY . .
USER 1000:1000
EXPOSE 8080
CMD ["bun", "index.ts"]

.git
node_modules
*.log
.env*
Dockerfile
.dockerignore

​

Deploy changes

​

Add a custom domain

​

Connect a database

​

Deploy with the API

• An API key with the Company developer role, or the APP:CREATE, APP:READ and APP:UPDATE permissions, in the SEVALLA_API_KEY environment variable. The CLI reads the key from SEVALLA_API_TOKEN.
• The repository on a Git provider that’s connected to your Sevalla account. See Git providers. Creating the application checks it: when Sevalla can’t read the repository, the call returns 400 with Cannot access repository https://github.com/acme/storefront: Repository not found or you don't have access., followed by where to grant access.
• curl and jq.

CLUSTER_ID=$(curl -s https://api.sevalla.com/v3/resources/clusters \
  -H "Authorization: Bearer $SEVALLA_API_KEY" \
  | jq -r '.[] | select(.location == "eu-frankfurt-1") | .id')

H1_ID=$(curl -s https://api.sevalla.com/v3/resources/process-resource-types \
  -H "Authorization: Bearer $SEVALLA_API_KEY" \
  | jq -r '.[] | select(.name == "h1") | .id')

APP_ID=$(curl -s -X POST https://api.sevalla.com/v3/applications \
  -H "Authorization: Bearer $SEVALLA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"display_name":"storefront","cluster_id":"'"$CLUSTER_ID"'","source":"privateGit","git_type":"github","repo_url":"https://github.com/acme/storefront","default_branch":"main"}' \
  | jq -r .id)

WEB_ID=$(curl -s https://api.sevalla.com/v3/applications/$APP_ID/processes \
  -H "Authorization: Bearer $SEVALLA_API_KEY" \
  | jq -r '.data[] | select(.type == "web") | .id')

curl -s -X PATCH https://api.sevalla.com/v3/applications/$APP_ID/processes/$WEB_ID \
  -H "Authorization: Bearer $SEVALLA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"resource_type_id":"'"$H1_ID"'"}' \
  | jq -c '{resource_type_name, cpu_limit, memory_limit}'

{"resource_type_name":"h1","cpu_limit":300,"memory_limit":300}

curl -s -X PATCH https://api.sevalla.com/v3/applications/$APP_ID \
  -H "Authorization: Bearer $SEVALLA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"auto_deploy":true}' | jq .auto_deploy

DEPLOYMENT_ID=$(curl -s -X POST https://api.sevalla.com/v3/applications/$APP_ID/deployments \
  -H "Authorization: Bearer $SEVALLA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}' | jq -r .id)

for i in $(seq 1 120); do
  STATUS=$(curl -s "https://api.sevalla.com/v3/applications/$APP_ID/deployments/$DEPLOYMENT_ID" \
    -H "Authorization: Bearer $SEVALLA_API_KEY" | jq -r '.status // empty')
  case $STATUS in success|failed|cancelled|skipped) break ;; esac
  sleep 15
done
echo "$STATUS"

curl -s "https://api.sevalla.com/v3/applications/$APP_ID/deployments/$DEPLOYMENT_ID/logs?limit=5000" \
  -H "Authorization: Bearer $SEVALLA_API_KEY" | jq -r '.[].message'

HOST=$(curl -s https://api.sevalla.com/v3/applications/$APP_ID/domains \
  -H "Authorization: Bearer $SEVALLA_API_KEY" \
  | jq -r '.data[] | select(.is_primary) | .name')
curl -s https://$HOST/

Hello from Bun on Sevalla

​

Build from the Dockerfile with the API

curl -s -X PATCH https://api.sevalla.com/v3/applications/$APP_ID \
  -H "Authorization: Bearer $SEVALLA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"build_type":"dockerfile","dockerfile_path":"Dockerfile","docker_context":"."}' \
  | jq -c '{build_type, dockerfile_path, docker_context}'

{"build_type":"dockerfile","dockerfile_path":"Dockerfile","docker_context":"."}