Templates
The template topic exists to close the gap between “I want to start
a new application in framework X” and “I have a repository the
platform can build and deploy”. One command produces a fresh
repository, pre-wired with the Dockerfile, flui.yaml, healthcheck,
and build pipeline a Flui-compatible repo needs — see Framework
templates for the conceptual
model.
flui template use <framework> <name>
Creates a new repository copied from the framework’s template and, by default, imports it into Flui so the application appears on the dashboard side immediately.
flui template use <framework> my-app # private repo, default orgflui template use <framework> my-app --public # public repoflui template use <framework> my-api --org my-org # under a specific orgflui template use <framework> my-svc -d "Internal microservice"flui template use <framework> my-app --no-import # skip the Flui-side import| Argument / Flag | Effect |
|---|---|
<framework> | Template name. Run flui template use --help for the list available today. |
<name> | Name for the new repository (required). |
--org <name> | Organisation or user to create the repo under. Default: your account. |
-d, --description <s> | Repository description. |
--public | Create as public. Default: private. |
--no-import | Create the repository on GitHub but skip the Flui-side import. |
Prerequisites
flui auth loginmust have been run — the command uses the active profile’s API key.- Your linked GitHub account needs permission to create a repository in the destination organisation. If the target is your personal account this is implicit; for an org, you (or the linked installation) must have repository-create rights there.