Skip to main content

Get set, go 🚀

Five minutes from now your app has a URL. All you need is an API token from whoever runs Pagifier at your company. No kubectl, no Docker, no cloud console, no sacrificial YAML.

This page does one manual deploy so you can see the whole loop. Once it works, let Pagifier watch Git or call the same deployment API from your CI system.

Nobody runs Pagifier for you yet?

No problem — install it yourself. The laptop version takes about 15 minutes, then come right back here.

1. Create pagifier.toml​

In your repository root:

pagifier.toml
version = 1

name = "my-app"
template = "react-static"
environment = "prod"
ingress = "my-app.company.com"

That's four lines of actual information — and that's the whole point. The react-static template already knows how to build a React app, where the output lands, what serves it, and how to cache it. The prod profile brings replicas, high availability, and rollout smarts. Your file only says what's unique about your app: its name, where it lives, and which recipe to follow.

Prefer YAML? pagifier.yaml with the same keys works identically.

Ask your platform team which templates exist — typical ones are react-static, vite-static, vue-static, nestjs, express, fastapi, and go-api.

2. Sanity-check it (10 seconds, zero regrets)​

curl -H "Authorization: Bearer $PAGIFIER_TOKEN" \
     --data-binary @pagifier.toml \
     https://pagifier.company.com/v1/validate

Good file? You get back the full picture — your four lines plus everything the templates filled in. Typo'd something? You get every problem at once, with suggestions, instead of a scavenger hunt:

{"valid": false, "errors": ["unknown field \"artefact\" — did you mean \"artifact\"?"]}

3. Ship it​

zip -r app.zip . -x '.git/*' -x 'node_modules/*'

curl -H "Authorization: Bearer $PAGIFIER_TOKEN" \
     -F config=@pagifier.toml \
     -F archive=@app.zip \
     "https://pagifier.company.com/v1/applications/my-app/environments/prod/deployments?wait=true"

That ?wait=true bit means you get to watch the whole thing happen:

{"releaseId":"r20260714-101530-ab12cd34","status":"Pending"}
{"phase":"Building"}
{"phase":"Built"}
{"phase":"Available","url":"https://my-app.company.com","done":true,"success":true}

And if the build blows up? The compiler output lands right there in your terminal. No kubectl safari required.

4. Shipped a stinker? Undo it​

Every deploy is a saved game. Rolling back is instant — the previous image just comes back, no rebuild, no drama:

curl -X POST -H "Authorization: Bearer $PAGIFIER_TOKEN" \
     https://pagifier.company.com/v1/applications/my-app/environments/prod/rollback

Where to next?​

  • Let Pagifier watch Git so merges build and reviewed release pins deploy: Deploy from Git
  • Keep CI in charge and reduce deployment to one pipeline step: CI integration
  • Follow a complete worked example: static site · backend API with secrets · monorepo
  • Get editor autocomplete: for TOML, add #:schema https://pagifier.company.com/v1/schema/pagifier.json as the first line (Even Better TOML / taplo); for YAML, use # yaml-language-server: $schema=… with the same URL.
  • See everything you can set: the configuration reference