rustlavel-cli

The rustlavel command: scaffold an application, run it, generate the parts of it.

Part of Rustlavel, a full-stack web framework for Rust written from scratch.

Install

cargo install rustlavel-cli

New applications

rustlavel new blog                  # asks what to put in
rustlavel new blog --with db,view   # or say so and skip the questions
rustlavel new app --with auth-kit   # sign-in, roles, audit trail, settings

Generators

rustlavel make:module reports       # a feature that owns its routes and permissions
rustlavel make:crud Post --fields "title:string,body:text,done:bool"
rustlavel make:controller Post
rustlavel make:service Payroll
rustlavel make:model Post
rustlavel make:migration add_status_to_posts

make:seeder, make:middleware, make:job, make:mail, make:notification, make:mcp-tool, make:package and make:docker are there too.

Running an application

rustlavel serve                     # reloads when files change
rustlavel route:list --path admin   # also --method and --name
rustlavel migrate
rustlavel db:seed
rustlavel doctor                    # diagnoses why the app will not start
rustlavel build                     # the single deployable binary

Commands that need the application itself — migrate, db:seed, route:list, queue:work — are forwarded to the project's own binary. On a deployed machine there is no cargo and no source, so you run that binary directly:

./app migrate
./app db:seed
./app queue:work

That is why rustlavel build produces one file: it is the administration tool as well as the server.

Upgrading a project

The starter kit is copied into your application, so it does not move when the framework does. This brings it forward:

rustlavel upgrade --dry-run        # say what would change, write nothing
rustlavel upgrade
rustlavel upgrade --from 0.5.0     # a project created before 0.7.2 has no manifest

It merges three versions of every file the kit owns: what the version in .rustlavel/manifest.json wrote, what is in your project now, and what this CLI would write. Where one side changed, that side wins. Where both changed, the file gets <<<<<<< markers and the project stops compiling until you resolve it — deliberately, because a half-applied upgrade found later is worse than a build that fails now.

The base is fetched from crates.io (with curl and tar, which is why doctor checks for them) and cached. Your own files are never touched.

Going from 0.5.0 to 0.7.2 is a large jump and has a step-by-step runbook: Upgrading to 0.7.2. Read step 7 before you run db:seed.

Documentation

• The repository
• The framework crate

Licence

MIT.