briqbriq

Ruby app

Your Ruby code running as a service, from files or a GitHub repo: it bundles the Gemfile and starts it. No image to build.

  • app
  • language

Guides: Run your own app, Run a GitHub repo

Run it

briq_run({
  recipe: "ruby",
  params: {
    "version": "3.4",
    "packages": [],
    "port": 8080,
    "env": {},
    "size": "small"
  },
  wait: true
})

Parameters

NameTypeOptionsDefault
versionenum3.4, 3.3"3.4"
filesrecord{ "path": "content" | { base64 } }—
repoobject{ url, ref?, dir?, token? }—
packagesstring[]—[]
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
appruby:3.4-slim8080small—

When to use it

  • You wrote a Sinatra, Roda or Rack app and want it running next to its database, without building an image.

Tips

  • Code in a repo: pass repo: { url: "github.com/owner/app" } instead of files. See Run a GitHub repo.
  • Pass the code as files: { "app.rb": "…", "Gemfile": "…" }. Relative paths go under /app, written before the app starts and again whenever it starts over.
  • The Gemfile is bundled at each start; packages: ["sinatra"] installs gems without one. Gems stay on the disk, so restarts are quick.
  • start is the command when it is not ruby app.rb, e.g. "bundle exec rackup -o :: -p 8080".
  • Listen on :: and on ENV["PORT"] (8080 by default).
  • 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