Deploy Deno
Falak deploys Deno apps from a repository with a deno.json or deno.jsonc. Deno is installed on each server the first time a Deno site targets it.
Prerequisites
Section titled “Prerequisites”- A server of type app, web or worker.
deno.json(ordeno.jsonc) with astarttask.- Your app listens on
Deno.env.get("PORT").
const port = Number(Deno.env.get('PORT') ?? 8000);const hostname = Deno.env.get('HOST') ?? '127.0.0.1';
Deno.serve({ port, hostname }, () => new Response('Hello from Deno on Falak'));{ "tasks": { "start": "deno run --allow-net --allow-env main.ts" }}Deploy
Section titled “Deploy”- + Create → Git repository, pick the repository.
- Choose the Generic Node preset and set the runtime to Deno.
- Pick servers and a domain, then Deploy.
How it runs
Section titled “How it runs”| Aspect | Value |
|---|---|
| Deno version | 2.9.7 (FALAK_DENO_VERSION), official release binaries |
| Detection | deno.json / deno.jsonc in the repository root (comments and trailing commas allowed) |
| Build | deno install (--frozen when deno.lock exists), then deno task build if defined |
| Web process | deno task start in the current release |
| Environment | Site variables + PORT, HOST=127.0.0.1 |
Limits
Section titled “Limits”- Deno at runtime is covered by unit and feature tests but not yet by Falak’s end-to-end test suite. Report issues you hit.
Deno.serveis not auto-instrumented; usewithFalakRequestfrom@falak/apm-node. See APM for Node, Bun and Deno.
Next steps
Section titled “Next steps”Static sitesDeploy Fresh or Lume output as a static site.
Environment variablesManage variables and references.