superpowers-sage:acorn-commands

Acorn CLI commands for WordPress automation require defining a command class with a $signature, $description, and a handle() method. You can use typed dependencies and Laravel services while executing WordPress functions within the same runtime.

Yes, you can use Laravel dependency injection inside WordPress scheduled jobs by building custom Acorn commands. These commands access Laravel container services and WordPress functions simultaneously, making them ideal for maintenance operations and derived-data recomputation.

Acorn CLI targets developer tooling like imports, cache warmups, and database recomputation rather than serving as a simple WP-CLI equivalent. It runs scheduled jobs and maintenance operations via lando acorn schedule:run, leveraging Laravel services and WordPress functions together.

You schedule and run Acorn commands in a Lando environment by executing them via lando acorn. You can list commands, view help text, and coordinate workflows by running lando acorn schedule:run to trigger scheduled jobs.

The best way to coordinate multiple Acorn commands during a data import is to call other commands silently or verbosely from within the handle() method. You can format output using info, warn, error, or table methods while supporting options like --dry-run.

Registering custom Acorn commands in WordPress optionally requires a service provider. You must have an Acorn-installed WordPress context to define your command signature and handle() method before executing it via the CLI.