briqbriq

Rust app

Your Rust crate running as a service, from files or a GitHub repo: it builds a release and runs it. No image to build.

  • app
  • language

Guides: Run your own app, Run a GitHub repo

Run it

briq_run({
  recipe: "rust",
  params: {
    "version": "1",
    "port": 8080,
    "env": {},
    "size": "small"
  },
  wait: true
})

Parameters

NameTypeOptionsDefault
versionenum1"1"
filesrecord{ "path": "content" | { base64 } }—
repoobject{ url, ref?, dir?, token? }—
installstring——
buildstring——
startstring——
portnumber—8080
envrecord{ NAME: "value" | { secret, value? } }{}
sizeenumnano, small, medium, large"small"
diskGbnumber——

Outputs

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

APP_URL
http://app.<stack>.internal:8080

What it runs

BriqImagePortsSizeVolume
apprust:1-slim8080small—

When to use it

  • You wrote an Axum, Actix or plain std::net service and want it built and running next to its database, without a Dockerfile or a registry.

Tips

  • Code in a repo: pass repo: { url: "github.com/owner/app" } instead of files. See Run a GitHub repo.
  • Pass the crate as files: Cargo.toml, Cargo.lock and src/main.rs (relative paths go under /app).
  • It builds a release at each start, then cargo run --release runs it, whatever the binary is called. target/ stays on the briq's disk, so a restart rebuilds in seconds; the first build downloads and compiles every dependency, so expect minutes for a big tree, and pick medium if the compiler runs out of memory.
  • Listen on [::]:$PORT (8080 by default): it takes IPv6 and IPv4.
  • Publish it as you run it with expose: "private" (or "public" for anyone): it returns URL.
  • 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