Falck config
One file to set the rules
Falck reads a `.falck/config.yaml` file in your repo. Define setup steps with checks, secrets, launch commands, and access URLs once. Falck enforces the workflow you already trust.
Core idea
Config describes the repo, Falck enforces the rules
The config defines how to install, configure, and launch each app in the repo. Falck turns it into a guided UI flow that non-technical teammates can follow without breaking anything.
`applications` list each app and its root path
Setup steps + checks keep setup safe
`setup` and `launch` steps define commands
.falck/config.yaml version 1.0
version: "1.0"
metadata:
name: "Falck Demo"
description: "Demo project"
repository:
default_branch: "main"
protect_default_branch: true
branch_prefix: "projects/"
applications:
- id: "web"
name: "Web App"
type: "web"
root: "."
secrets:
- name: "DATABASE_URL"
required: true
setup:
steps:
- name: "Install Node 18"
command: "brew install node@18"
check:
command: "node --version"
expect_regex: "^v18"
teardown:
command: "brew uninstall node@18"
- name: "Install dependencies"
command: "bun install"
check:
command: "test -d node_modules"
launch:
command: "bun run dev"
access:
type: "http"
url: "http://localhost:3000"
port: 3000
open_browser: true
TL;DR
Configure once, keep control forever
The config lives next to your code and stays versioned. Everyone gets the same setup, the same guardrails, and the same happy reviews.