v0.1.0-beta.2

The Tiger platform framework — the Tiger_* kernel + multi-tenant substrate (org / user / org_user / ACL) on TigerZF. Installable from Packagist.

Beta. Functional and dogfooded on tiger-dev; the @api surface may still shift between beta releases.

Install

# a new app (skeleton + framework, from Packagist)
composer create-project webtigers/tiger my-app --stability=beta

# or add the framework to an existing app
composer require webtigers/tiger-core:^0.1.0-beta

What's new since beta.1

Module lifecycle — assets + dependencies

• make:module now scaffolds optional layouts/, assets/, and configs/dependency.ini stubs (a module can be theme-agnostic or pure /api).
• Assets on activate — a module's assets/ (if it has one) is symlinked into public/_modules/<slug> on module:activate and removed on module:deactivate. No copy, failsafe (Tiger_Module_Installer::publishAssets / unpublishAssets).
• Dependency alerts — Tiger_Module_Dependency reads configs/dependency.ini lazily (zero boot cost, only when toggling): activate warns of required modules that aren't active ("requires X, Y to activate"); deactivate surfaces modules that depend on this one. Convenience alerts — never a hard block. Wired into bin/tiger module:activate|deactivate and the admin module manager.

Failsafe asset wiring (cPanel-ready)

• bin/tiger link:assets + Tiger_Install::linkPublicAssets() — (re)create the webroot's _theme/_tiger symlinks with absolute targets computed from the app root. Idempotent, won't clobber a real directory, and --webroot handles the cPanel split layout (~/public_html above the app). The recommended way to wire assets on any host.

The companion skeleton change (public/index.php self-locates the app root for cPanel) ships in webtigers/tiger v0.1.0-beta.2+.

Links

• Changelog: CHANGELOG.md
• Diff: v0.1.0-beta.1...v0.1.0-beta.2
• Packagist: webtigers/tiger-core