briqbriq

Static site

HTML, CSS, JavaScript and images served by nginx, from files or a folder of a GitHub repo. No build, no image.

  • app
  • language

Guides: Run your own app, Run a GitHub repo

Run it

briq_run({
  recipe: "static",
  params: {
    "size": "nano"
  },
  wait: true
})

Parameters

NameTypeOptionsDefault
filesrecord{ "path": "content" | { base64 } }—
repoobject{ url, ref?, token?, dir? }—
sizeenumnano, small"nano"

Outputs

Returned by briq_run once the stack is healthy. Hosts resolve inside your team network; secrets are generated per run.

SITE_URL
http://site.<stack>.internal

What it runs

BriqImagePortsSizeVolume
sitenginx:1-alpine80nano—

When to use it

  • A page, a report or a small site the agent generated, and a URL to send someone.
  • A built frontend (the output of vite build) that needs no server of its own.

Tips

  • A site on GitHub: repo: { url: "github.com/owner/site", dir: "public" } serves that folder as it is, downloaded by the briq itself: Run a GitHub repo. A site with a build step runs on the node recipe.
  • Pass the site as files: { "index.html": "…", "app.js": "…" }, images as { "base64": "…" }. Relative paths go under nginx's root; index.html is the home page.
  • 256 KB in all: for a bigger site, write the files with briq_files_put once it runs, or fetch them from inside with briq_exec (wget).
  • Publish it as you run it: briq_run({ recipe: "static", params: { files }, expose: "private" }) returns a URL only the people you send it to can open.
  • Step by step: Run your own app, with a database and a URL.

On this page

Free to try

Let your agent try it, on us.

Every new account starts with €10 of credits. No card.

Connect your agent

How can we help?

Message to the briq team
hello@briq.cloud