These libraries are experimental. APIs may change without notice. Generated from source with koruc 0.1.7 on 11/17/2026.
Fly
@korulang/flyDeclarative app configs collected at compile time; `koruc <file>.k fly`
fly/index.kz · 2 tors
@korulang/fly - Fly.io deployment DSL for Koru · 33 more lines
@korulang/fly - Fly.io deployment DSL for Koru
Declarative app configs collected at compile time; `koruc <file>.k fly`
commands emit fly.toml and drive flyctl. Orphan of the docker package's
shape: declarations live in the program, the command walks the AST.
DECLARATIVE CONFIG — the body is a JSON object, the same shape
requires.system / command.declare already speak:
import koru/fly
koru/fly:config(app: "korulang-debug") {
"region": "ams",
"build": "--build=linux --release=fast",
"http_service": {
"internal_port": 3000,
"force_https": true,
"auto_stop_machines": "stop",
"auto_start_machines": true,
"min_machines_running": 0
},
"vm": [{ "size": "shared-cpu-1x", "memory": "256mb" }]
}
JSON objects emit as TOML tables ([http_service]), arrays of objects as
arrays of tables ([[vm]]), scalars as key/value. Reserved keys are consumed
by the command, not emitted: "region" → primary_region, "dockerfile" →
build's dockerfile, "build" (object) → the [build] table, "build" (string)
→ koruc flags for the rebuild step, "app" → ignored (the argument owns it).
Then: koruc main.k (builds a.out)
koruc main.k fly deploy (emits fly-<app>.toml, runs flyctl)
koruc main.k fly config (emit only)
~[comptime|command] pub tor fly {
program: *const Program,
allocator: __koru_std.mem.Allocator,
argv: []string
}// Declarative Config (compile-time, collected by the fly command)
~[comptime|norun] pub tor config { app: Expression, source: Source }