Deployment

Install from Packagist

A new app is one line — it pulls the skeleton + framework (tiger-core, tigerzf) and their deps, no clone, no build step:

composer create-project webtigers/tiger my-app --stability=beta

The --stability=beta flag drops away at the stable 1.0. (A pre-built vendored ZIP + a browser web installer for no-shell / cPanel hosts is on the roadmap.)

Works on any web server

A zero-config public/.htaccess (front-controller routing) is the default — drop the app on Apache and it runs. Reference configs ship for an Apache vhost (the faster form), nginx, and Caddy/FrankenPHP. Asset URLs are root-relative and protocol-agnostic, so staging → prod moves and ALB/proxy setups just work.

Update-safe by construction

Framework code lives in vendor/ and is replaced by composer update; everything you own lives outside it. You never edit Tiger — you extend it (modules, config .ini overrides, subclasses). So an update can't clobber your work.

  • With a shell: composer update.
  • Without one: the one-click Updates screen — download → verify → apply → migrate, including a no-shell atomic core self-update. No FTP, no Composer.

Shared hosting is a first-class target

Everything stays inside the account folder — no vhost edits, no system-tmp, no infrastructure a module install depends on. Tiger is built to run on cPanel/shared hosting, not just a VPS.

See also