capy-cli 0.1.0

Project scaffolding, generators, and development commands for the Capy web framework.
Documentation

capy-cli

Project scaffolding, generators, and development commands for the Capy web framework.

cargo install capy-cli
capy new blog
cd blog
capy serve

Requires Rust and rustfmt. capy serve is for local development. For deployment, run cargo build --release and the compiled application binary directly.

Generators hold a cross-process project lock while checking names and updating registries. A successful capy make:* creates every required file and registration; a failed command makes a best effort to restore the previous valid state. Registries are replaced atomically, and a failed replacement removes the new source file. Keep .capy-generator.lock in place; the lock file is intentionally persistent and ignored by Git. Do not edit registries concurrently with a generator. Locks require a filesystem supporting advisory locks and atomic rename. Power loss or SIGKILL between source creation and registry replacement can leave an unregistered source; inspect and remove or register that source before retrying.

Names normalize to snake_case modules and PascalCase types. Model exports also reserve <Type>Model. Collisions are rejected before source changes. Registry imports must be explicit; glob imports and binding-generating macros in ordinary registries prevent reliable collision checks. Migration registry markers must each occur exactly once.

On Unix, Capy owns the server directly, forwards SIGINT/SIGTERM to its process group, allows five seconds to shut down, then kills and reaps the child if needed. Exit status is preserved (128 + signal for signal deaths). Windows console Ctrl-C uses console signal delivery; forced termination of the Capy PID by a Windows process manager is not supported. Use the compiled binary directly there.

MIT licensed. See LICENSE. This is an initial developer preview, not a production-readiness claim.