The bin/tiger console

bin/tiger is the platform's command line. It boots through the same path as a web request (Tiger_Application::boot()), so a command gets the identical constants, config cascade, and DB adapter — no second, drifting bootstrap.

Commands

Schema

  • migrate · migrate:status · migrate:rollback — run / inspect / undo migrations (core, app, and every module's migrations/).

Install & secrets

  • install:secrets — mint the install's random secrets (app encryption key + password/code pepper) into local.ini if missing (idempotent).
  • install:admin — create the founding org + owner (also provisions secrets).

Secret rotation (zero-downtime — see Auth & sessions)

  • crypto:rotate-key + crypto:rekey — re-encrypt reversible data under a new key, losslessly.
  • security:rotate-pepper — rotate the one-way password/code pepper (re-peppers lazily on next login).
  • secrets:drop-retired [crypto|pepper|all] — remove a retired secret once migration is confirmed.

Modules

  • make:module <name> — scaffold a live module (controller + /api service + ACL + views + config).
  • module:install|remove|list|activate|deactivate — manage modules from the shell.

Assets & info

  • link:assets — (re)create the public asset symlinks.
  • version.

No shell? No problem

Everything an operator needs day-to-day — updates, module install/activate, settings — is also in the admin back office, because Tiger targets hosts where you may have no shell at all. The CLI is for developers and automation; the Updates screen and Module Manager cover the no-shell path.