Run Puppeteer

​

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.
• Node.js 24 or later on your computer.

​

Create the project

mkdir storefront && cd storefront
npm init -y
npm install puppeteer
npx puppeteer browsers install chrome
npm pkg set type=module scripts.start="node server.js" engines.node="24.x"

import http from "node:http";
import puppeteer from "puppeteer";

const browser = await puppeteer.launch({
  args: ["--no-sandbox", "--disable-dev-shm-usage"],
});

const server = http.createServer(async (req, res) => {
  if (req.url !== "/screenshot") {
    res.writeHead(200, { "Content-Type": "text/plain" });
    res.end("Open /screenshot to capture https://example.com");
    return;
  }

  const page = await browser.newPage();
  try {
    await page.goto("https://example.com");
    const image = await page.screenshot({ type: "png" });
    res.writeHead(200, { "Content-Type": "image/png" });
    res.end(image);
  } catch (error) {
    res.writeHead(500, { "Content-Type": "text/plain" });
    res.end(String(error));
  } finally {
    await page.close();
  }
});

server.listen(process.env.PORT || 3000);

process.on("SIGTERM", async () => {
  await browser.close();
  server.close(() => process.exit(0));
});

node_modules/

​

Prepare the project for Sevalla

• npm ci runs with PUPPETEER_SKIP_DOWNLOAD set, so the install doesn’t download Chrome into the build.
• The final image runs puppeteer browsers install chrome --install-deps, which installs the Chrome release your Puppeteer version expects into /usr/local/share/puppeteer, with the Debian packages Chrome needs.
• The image sets PUPPETEER_CACHE_DIR to /usr/local/share/puppeteer, so puppeteer.launch() finds that Chrome.

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: Node.js 24 from engines.node, npm from package-lock.json and the start command from the start script.
   Build log

   ╭─ ■ Node.js 24 application ───────────────────────────────────╮
   │ Node.js          24              package.json engines "24.x" │
   │ Package manager  npm             package-lock.json           │
   │ Start            node server.js  package.json scripts.start  │
   ├─ Image ──────────────────────────────────────────────────────┤
   │ Build            node:24-trixie                              │
   │ Runtime          node:24-trixie-slim                         │
   │ User             1000:1000                                   │
   │ Init             tini                                        │
   │ Port             $PORT, default 8080                         │
   ╰─────────────────────────────────────────────── Ingot v0.5.0 ─╯
   
   Further down, the step that installs Chrome prints the release and its path, such as chrome@156.0.8078.47 /usr/local/share/puppeteer/chrome/linux-156.0.8078.47/chrome-linux64/chrome.
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, and add /screenshot to the address. The page shows a screenshot of https://example.com.
4. Check the same address from a terminal:
   curl -s https://storefront-x7k2m.sevalla.app/; echo
   curl -s -o screenshot.png -w '%{http_code} %{content_type}\n' https://storefront-x7k2m.sevalla.app/screenshot
   
   Open /screenshot to capture https://example.com
   200 image/png
   

• Could not find Chrome means the image has no Chrome: check that puppeteer is in dependencies, not devDependencies.
• A process that stops without an error usually ran out of memory: scale the web process to a larger size.

​

Add fonts for other languages

​

Deploy with a Dockerfile

FROM node:24-trixie-slim

# Debian's packages get the base image's security updates, so they aren't pinned
# hadolint ignore=DL3008
RUN apt-get update \
  && apt-get install -y --no-install-recommends chromium fonts-liberation tini \
  && rm -rf /var/lib/apt/lists/*

WORKDIR /app
ENV NODE_ENV=production PORT=8080 \
  PUPPETEER_SKIP_DOWNLOAD=true PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium

COPY package.json package-lock.json ./
RUN npm ci --omit=dev && npm cache clean --force

COPY . .

USER 1000:1000
EXPOSE 8080
ENTRYPOINT ["tini", "--"]
CMD ["node", "server.js"]

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

​

Deploy changes

​

Run browser jobs in the background

​

Add a custom domain

​

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')

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)

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/; echo
curl -s -o screenshot.png -w '%{http_code} %{content_type}\n' https://$HOST/screenshot

Open /screenshot to capture https://example.com
200 image/png

​

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":"."}

​

Add fonts with the API

curl -s -X POST https://api.sevalla.com/v3/applications/$APP_ID/env-vars \
  -H "Authorization: Bearer $SEVALLA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"key":"INGOT_RUN_PACKAGES","value":"fonts-noto-core fonts-noto-cjk"}' \
  | jq -c '{key, is_runtime, is_buildtime}'

{"key":"INGOT_RUN_PACKAGES","is_runtime":true,"is_buildtime":true}

curl -s -G "https://api.sevalla.com/v3/applications/$APP_ID/deployments/$DEPLOYMENT_ID/logs?limit=5000" \
  -H "Authorization: Bearer $SEVALLA_API_KEY" \
  --data-urlencode "search=Setting up fonts-noto" \
  | jq -r '.[].message | sub("^#[0-9]+ [0-9.]+ "; "")'

Setting up fonts-noto-mono (20201225-2) ...
Setting up fonts-noto-cjk (1:20240730+repack1-1) ...
Setting up fonts-noto-core (20201225-2) ...