mix phoenix_kit.status (phoenix_kit v1.7.230)

Copy Markdown View Source

Shows comprehensive status of PhoenixKit installation.

This task provides a detailed overview of your PhoenixKit installation status, including version information, database connectivity, assets status, and suggested next actions.

Usage

$ mix phoenix_kit.status
$ mix phoenix_kit.status --prefix=myapp

Options

  • --prefix - Database schema prefix. When omitted, resolves from config :phoenix_kit, :prefix, then defaults to "public".
  • --verbose - Show detailed diagnostic information

Examples

# Show status for default installation
mix phoenix_kit.status

# Show status for custom schema prefix
mix phoenix_kit.status --prefix=auth

# Show detailed diagnostic information
mix phoenix_kit.status --verbose

Sample Output

PhoenixKit v1.7.216
├── Installed: V159 ✅
├── Database: Connected ✅
├── Modules: 2 modules, all up to date ✅
│   ├── Boards: V01 ✅
│   └── Inbox: V01 ✅
└── Next: Ready

The Modules row covers PhoenixKit modules that own their migrations (PhoenixKit.Module.migration_module/0) — each reports the schema version installed in your database against the version its code expects. When one is behind, the report says so and Next points at the fix:

PhoenixKit v1.7.216
├── Installed: V159 ✅
├── Database: Connected ✅
├── Modules: 2 modules, 1 update available ⬆
│   ├── Boards: V01 ✅
│   └── Inbox: V01 → V02 available ⬆
└── Next: mix phoenix_kit.update (module schema behind: Inbox)

The row is omitted entirely when no installed module owns migrations, so a core-only install keeps the compact tree.