Templates
The template topic takes you from “I want to start a new
application in framework X” to a repository the platform can build
and deploy. One command creates a new repository that already has
the Dockerfile, flui.yaml and healthcheck Flui needs. See
Framework templates for the
concepts.
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 in the dashboard right away. If a repository with that name already exists and was made from the same template, it is reused.
flui template use <framework> my-app # private repo, default ownerflui 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: nextjs, nuxt, angular, sveltekit, astro, vue-vite, vitepress, nestjs, spring-boot, django, fastapi, aspnet-core or generic. |
<name> | Name for the new repository (required). |
--org <name> | Organisation or user to create the repo under. Default: your linked GitHub account, or, with the Flui GitHub App, an account it is installed on that you can reach. |
-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
- You have run
flui auth login. 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.