summercms/docs/console/setup-and-maintenance.md

title, description, section, order

title	description	section	order
Setup and maintenance	Every runtime command of an application binary, with its flags and purpose, from migrations and the server to workers, admin accounts and realtime checks.	console	20

Setup and maintenance

Every application binary carries the framework's runtime commands. The examples use a binary named acme; yours is named by binary: in summer.yaml.

Migrations

Command	Flags	Purpose
migrate	none	Runs the framework migrations, then every plugin's migrations in dependency order.
migrate:rollback	--plugin <id>	Rolls back the last migration of the plugin; without the flag, of the last activated plugin that has migrations.
migrate:status	none	Prints a table of plugin, history table and applied migration IDs.

./bin/acme migrate
./bin/acme migrate:status
./bin/acme migrate:rollback --plugin acme.blog

Each plugin keeps its own migration history table, so rolling back one plugin never touches another. The migrations are listed in lagoon.

Pending uploads and related records

An admin form holds the files uploaded and the related records created for a record that is not saved yet as deferred bindings. Saving the record commits them; abandoned ones are removed by deferred:purge:

Command	Flags	Purpose
deferred:purge	--days <n>	Deletes deferred bindings older than n days, the unattached uploads they hold and the records created under deferral, and prints the counts. Records that were only linked are kept. Without the flag, database.deferred_bindings.purge_days applies, else 5 days.

./bin/acme deferred:purge
./bin/acme deferred:purge --days=1

The scheduler already runs it every day at 03:00; see Task scheduling.

Application key

Command	Flags	Purpose
key:generate	none	Prints a fresh base64 32-byte key for app.key. It writes nothing and needs no database.

./bin/acme key:generate

Copy the printed value into SUMMER_APP__KEY. When you rotate the key, keep the old one in app.previous_keys so existing encrypted columns can still be read.

The HTTP server

Command	Flags	Purpose
serve	--addr (default :8080)	Opens the database and uploads bucket, builds the router, binds the address, starts the in-process job worker and serves HTTP until SIGINT or SIGTERM, then shuts down within 10 seconds. After binding it prints the listen address with a browser URL (an unspecified host shows as 127.0.0.1) and an admin status line: the admin URL, or admin: off with the steps to add an admin controller.
route:list	none	Builds the router the way serve does, without opening the database or listening, and prints every route with its method, pattern, plugin, middleware and raw flag, followed by the admin status line.

./bin/acme route:list
./bin/acme serve --addr 127.0.0.1:8080

The default --addr listens on every interface. Pass a loopback address during development, and put a reverse proxy in front of the binary in production. The routing options are in surf.

From the application directory, summer serve --addr 127.0.0.1:8123 passes the flag through to the built binary.

Admin accounts

Command	Arguments and flags	Purpose
admin:create	--email (required), --login, --role <code>, --superuser, --password (deprecated)	Creates an activated backend administrator. --login defaults to the lower-cased email. The password is read from a hidden prompt, or from stdin when the input is not a terminal.
admin:reset-password	<identifier> (login or email), --password (deprecated)	Sets a new password, read like the one of admin:create, and revokes every JWT issued before the reset. Personal API tokens are unchanged.
admin:token:create	<identifier>, --name, --scope (repeatable), --expires (30d, 90d, 365d, never, or YYYY-MM-DD)	Creates a personal API token for the named administrator and prints exactly the plaintext and a newline on stdout.
admin:token:list	[<identifier>], --revoked	Lists tokens (hint only, never the hash or plaintext).
admin:token:revoke	<id>	Soft-revokes any user's active token by id.
admin:token:scopes	none	Lists framework and plugin scopes available for tokens.

./bin/acme admin:create --email admin@example.com --superuser
./bin/acme admin:reset-password admin@example.com
TOKEN=$(./bin/acme admin:token:create admin@example.com --name agent --scope blog)

admin:create and admin:reset-password prompt for the password without echoing it. In a script, pipe it on stdin, for example printf '%s\n' "$ADMIN_PASSWORD" | ./bin/acme admin:create --email admin@example.com --superuser. The --password flag still works but is deprecated and prints a warning, because the value stays in your shell history and is visible in the process list. The admin and personal API tokens are described in cabana and Users and permissions.

From the application directory, summer admin:create --email admin@example.com --superuser runs the same command on the built binary, prompt included. The four admin:token:* commands have matching summer delegates.

When the admin is mounted and the backend_users table is empty, serve prints a warning at start-up naming summer admin:create.

Queues and the scheduler

Command	Arguments and flags	Purpose
queue:work	--queue <name>, repeatable	Runs a job worker in the foreground on the named queues (default: every known queue) until SIGINT or SIGTERM. An unknown queue is an error that lists the known ones.
queue:clear	[queue] (default default)	Deletes the waiting, scheduled and retryable jobs of one queue and prints how many it cleared. Running jobs are never touched.
schedule:run	--once	Without --once, runs a scheduler-only worker until stopped. With --once, runs the entries due in the current minute and exits, for system cron.

./bin/acme queue:work --queue default --queue imports
./bin/acme queue:clear imports
./bin/acme schedule:run --once

serve runs a job worker in the same process unless queue.work_in_serve is false; set it to false when you run queue:work separately. Task scheduling explains the scheduler, and conga the queue settings.

Realtime and push

These commands are not added by the generated main. An application that uses Centrifugo or Web Push appends them to the list one of its plugins returns from pact.HasCommands: centrifugo.Commands returns websockets:health, and flare.Commands returns the two push commands.

Command	Arguments and flags	Purpose
websockets:health	none	Calls the Centrifugo info API and prints the configuration. Exits 1 when the API key is missing or the call fails. The key itself is never printed.
websockets:generate-vapid-keys	--update, --show-current	Shows the configured VAPID keys, truncated, then generates a new pair. With --update it saves them to the environment's overrides.yaml; without it, it prints the variables to set by hand.
websockets:test-push	<user_id>, --show-config	Lists a user's push subscriptions and, after confirmation, sends one encrypted test notification to each.

./bin/acme websockets:health
./bin/acme websockets:generate-vapid-keys --show-current
./bin/acme websockets:test-push 1

The settings are in lighthouse and flare.