brightery/app

Application skeleton for Brightery Framework.

Maintainers

Package info

github.com/Brightery/brightery-app

Type:project

pkg:composer/brightery/app

Transparency log

Statistics

Installs: 1

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

Security

Advisories: 0

Aikido package health analysis

v1.0.1 2026-08-05 18:46 UTC

Requires

MIT 0c9a65fac53ebfa429ed80e1b0a3772d91fd5048

Published on Packagist.org on 2026-08-05 18:47 UTC

This package is auto-updated.

Last update: 2026-08-05 18:48:32 UTC

README

A Composer-ready application skeleton for Brightery Framework stable 1.x.

Create a project

composer create-project brightery/app my-project "^1.0"
cd my-project
php vendor/bin/brightery app:install
php vendor/bin/brightery doctor
php vendor/bin/brightery serve

Production build

php vendor/bin/brightery optimize
php vendor/bin/brightery schema:plan database/schema
php vendor/bin/brightery runtime:soak --iterations=5000 --json
php vendor/bin/brightery audit:verify
php vendor/bin/brightery release:check --production --json

Expose only public/ through the web server. Do not deploy composer.local.json; the release builder excludes it automatically.

Stable upgrade diagnostics

php vendor/bin/brightery upgrade:plan --json
php vendor/bin/brightery upgrade:scan . storage/upgrade/report.json
php vendor/bin/brightery api:check previous-api-surface.json

Integration fixtures

docker compose -f docker-compose.integration.yml up -d
php vendor/bin/brightery integration:doctor
BRIGHTERY_INTEGRATION=1 php vendor/bin/brightery integration:test

The environment includes MySQL, Redis, MinIO, Mailpit, OTLP Collector, MockServer, and an optional gateway profile.

Persistent workers

bootstrap/worker.php, bootstrap/roadrunner.php, and bootstrap/frankenphp.php provide bounded request-scope lifecycle boundaries. Run live transport tests and a workload-specific soak test before enabling persistent workers in production.

Modules and realtime

Signed modules require trusted public keys, verified file manifests, compatible framework constraints, and valid dependency graphs. Presence/private channels require application-issued signatures and Redis-backed presence when gateways are scaled horizontally.