Management commands
This page provides a reference for all the available management commands and their options.
collectassets
Usage: marten collectassets [options]
Collects all the assets and copies them into a unique storage.
Please refer to Asset handling to learn more about when and how assets are "collected".
Options
--no-input- Does not show prompts to the user
Examples
marten collectassets # Collects all the assets
marten collectassets --no-input # Collects all the assets without any prompts
genmigrations
Usage: marten genmigrations [options] [app_label]
Generates new database migrations.
This command will scan the table definition corresponding to your current models and will compare it to the equivalent tables that are defined by your migration files. Based on the result of this analysis, a new set of migrations will be created and persisted in your applications' migrations folders. Please refer to Migrations to learn more about this mechanism.
Options
--empty- Creates an empty migration
Arguments
app_label- The name of an application to generate migrations for (optional)
Examples
marten genmigrations # Generates new migrations for all the installed apps
marten genmigrations foo # Generates new migrations for the "foo" app
marten genmigrations foo --empty # Generates an empty migration for the "foo" app
listmigrations
Usage: marten listmigrations [options] [app_label]
Lists all the available database migrations.
This command will introspect your project and your installed applications to list the available migrations, and indicate whether they have already been applied or not. Please refer to Migrations to learn more about this mechanism.
Options
--db=ALIAS- Allows specifying the alias of the database on which migrations will be applied or unapplied (default todefault)
Arguments
app_label- The name of an application to list migrations for (optional)
Examples
marten listmigrations # Lists all the migrations for all the installed apps
marten listmigrations foo # Lists all the migrations of the "foo" app
migrate
Usage: marten migrate [options] [app_label] [migration]
Runs database migrations.
The migrate command allows you to apply (or unapply) migrations to your databases. By default, when executed without arguments, it will execute all the non-applied migrations for your installed applications. That being said, it is possible to ensure that only the migrations of a specific application are applied by specifying an additional app_label argument. To unapply certain migrations (or to apply some of them up to a certain version only), it is possible to specify another migration argument corresponding to the version of a targetted migration. Please refer to Migrations to learn more about this mechanism.
Options
--fake- Allows marking migrations as applied or unapplied without actually running them--plan- Provides a comprehensive overview of the operations that will be performed by the applied or unapplied migrations--db=ALIAS- Allows specifying the alias of the database on which migrations will be applied or unapplied (default todefault)
Arguments
app_label- The name of an application to run migrations formigration- A migration target (name or version) up to which the DB should be migrated. Usezeroto unapply all the migrations of a specific application
Examples
marten migrate # Applies all the non-applied migrations for all the installed apps
marten migrate foo # Applies migrations for the "foo" app
marten migrate foo 202203111821451 # Applies (or unapply) migrations for the "foo" app up until the "202203111821451" migration
new
Usage: marten new [options] [type] [name]
Initializes a new Marten project or application structure.
The new management command can be used to create either a new project structure or a new application structure. This can be handy when creating new projects or when introducing new applications into an existing project, as it ensures you are following Marten's best practices and conventions.
The command allows you to fully define the name of your project or application, and in which folder it should be created.
Options
-d DIR, --dir=DIR- An optional destination directory--with-auth- Adds an authentication application to newly created projects. See Authentication to learn more about this capability
Arguments
type- The type of structure to create (must be eitherprojectorapp)name- The name of the project or app to create
The type and name arguments are optional: if they are not provided, an interactive mode will be used and the command will prompt the user for inputting the structure type, the app or project name, and whether the auth app should be generated.
Examples
marten new project myblog # Creates a "myblog" project
marten new project myblog --dir=./projects/myblog # Creates a "myblog" project in the "./projects/myblog" folder
marten new app auth # Creates an "auth" application
resetmigrations
Usage: marten resetmigrations [options] [app_label]
Resets an existing set of migrations into a single one. Please refer to Resetting migrations to learn more about this capability.
Arguments
app_label- The name of an application to reset migrations for
Examples
marten resetmigrations foo # Resets the migrations of the "foo" application
routes
Usage: marten routes [options]
Displays all the routes of the application.
serve
Usage: marten serve [options]
Starts a development server that is automatically recompiled when source files change.
Options
-b HOST, --bind=HOST- Allows specifying a custom host to bind-p PORT, --port=PORT- Allows specifying a custom port to listen for connections
Examples
marten serve # Starts a development server using the configured host and port
marten serve -p 3000 # Starts a development server by overriding the port
You can also use the alias s to start the development server:
marten s
version
Usage: marten version [options]
Shows the Marten version.