Expand description
The siderite command line.
Two entry points:
AppCliis the command line of an application binary. It needs the application’sAppand model metadata, so it can serve the app (run), list its routes, validate it (check), open a database shell and run every migration command includingmakemigrations.runis thesideritebinary. In a Cargo package it wrapscargo runfor those commands;newwrites a project; without a package it runs JSON-filemigrate/rollback/showmigrations/squashmigrations.
Re-exports§
pub use check::CheckIssue;pub use check::CheckLevel;pub use check::check;pub use connect::connect_url;pub use dbshell::ShellCommand;pub use routes::RouteRow;pub use routes::render_routes;pub use routes::route_table;pub use seed::SeedError;pub use seed::Seeding;pub use settings::CliSettings;pub use settings::DEFAULT_ADDR;
Modules§
- check
check: validate the app, its models and its configuration without starting a server or opening a database.- commands
- The command contract: one table describing every
sideritecommand. - connect
- Open a
Dbfrom a database URL. - dbshell
dbshell: start the backend’s native client (sqlite3,psql,mysql).- report
- Typed reports and the output contract shared by the text and JSON renderers.
- routes
routes: the table ofMETHOD PATH operation_idan app serves.- seed
seed --dataset NAMEandseed --list: datasets the application registers withAppCli::seed, loaded only when asked for, into the database the global flags select.- settings
- The settings the command line needs, as plain values.
Structs§
- AppCli
- The commands that need the application’s own
Appand models, so they run from the application binary rather than the standalonesideritetool.
Enums§
Functions§
- run
- Entry point of the
sideritebinary.