Download the PHP package waaseyaa/waaseyaa without Composer
On this page you can find all versions of the php package waaseyaa/waaseyaa. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download waaseyaa/waaseyaa
More information about waaseyaa/waaseyaa
Files in waaseyaa/waaseyaa
Package waaseyaa
Short Description Waaseyaa CMS project skeleton
License GPL-2.0-or-later
Informations about the package waaseyaa
Waaseyaa Application
A Waaseyaa CMS application.
New project
Use ./vendor/bin/waaseyaa for the CLI. Optional path-linked waaseyaa/* checkouts: copy composer.local.json.example to composer.local.json (see docs/local-dev.md).
Directory Structure
Domain Rules
Bounded contexts go under Domain/<ContextName>/ with optional subdirectories:
Service/, ValueObject/, Workflow/, Assembler/, Ranker/, Mapper/.
Support Rules
Cross-cutting utilities (validators, slug generators, normalizers, distance
calculators) belong in Support/.
Namespace Rules
Namespaces must match PSR-4 directory structure. Update namespaces in files and all references when moving code.
Commands
Required PHP extensions
This app defaults to a SQLite database (storage/waaseyaa.sqlite), so the PHP
runtime must have pdo_sqlite and sqlite3 (and sodium). These are
declared in composer.json, so composer install flags a runtime missing them.
Serving with FrankenPHP (composer run dev)
composer run dev runs the app on FrankenPHP — the real
concurrent runtime — in classic per-request mode, bound to loopback on a
non-privileged port (no privileged-port or HTTPS-certificate prompt):
The first run downloads the FrankenPHP binary for you (via the optional
waaseyaa/frankenphp package, installed by default in the skeleton) — so there
is nothing to download or place by hand. If the binary isn't present yet,
composer run dev offers to fetch it; you can also do it up front:
It works identically on Windows, macOS, and Linux with zero PATH setup.
composer run dev routes to the waaseyaa dev command via Composer's own PHP
(@php), which resolves the frankenphp binary to an absolute path and execs
it directly — you never add the FrankenPHP directory to PATH.
Do NOT put the FrankenPHP directory on
PATH. The official Windows release is a full PHP SDK that bundles its ownphp.exewith OpenSSL disabled — onPATHit shadows your system PHP and breaks Composer (TLS to Packagist fails).waaseyaa devsidesteps this entirely: it execsfrankenphpby absolute path and never invokes the bundledphp.exe.
Binary resolution order: FRANKENPHP_BIN (an absolute path) → the managed
install from frankenphp:install (under vendor/bin/) → a known install location
(%USERPROFILE%\.frankenphp\frankenphp.exe on Windows; /usr/local/bin,
/usr/bin, /opt/homebrew/bin, ~/.frankenphp on macOS/Linux) → frankenphp on
PATH. If none resolve, composer run dev prints exactly what to do (and offers
to install). Override the listen address with WAASEYAA_DEV_LISTEN, or point at a
custom binary:
Classic mode uses FrankenPHP's built-in SQLite — no php.ini hack needed.
./vendor/bin/waaseyaa serve remains the zero-dependency php -S dev server (no
FrankenPHP required); it is fine for quick edits but is not the right runtime
for the admin SPA's live /api/broadcast SSE connection or for production.
Worker mode (advanced). For the warm, worker-mode runtime (best for heavy
SSE), run FrankenPHP natively against the committed config/frankenphp/:
Use PHP_INI_SCAN_DIR (additive), never PHPRC — PHPRC replaces the
runtime's bundled php.ini, which on shared-extension builds (e.g. the official
Windows release) strands pdo_sqlite/sqlite3 and 500s every request with
could not find driver. The committed php.ini does not enable those extensions
itself (mainstream builds already provide them); uncomment its extension= lines
only for a custom build that genuinely lacks SQLite.
Upgrading the framework
This skeleton requires waaseyaa/framework with a caret constraint
(^0.1.0-alpha.NNN), so a plain composer update waaseyaa/framework takes the
next point release. Keep it a caret:
Avoid
composer require waaseyaa/framework:0.1.0-alpha.NNN— an exact version writes a pinned constraint, and thencomposer updatesilently does nothing on later releases. Usecomposer require waaseyaa/framework:^0.1.0-alpha.NNN(with the caret) if you ever re-add it.
First 60 Seconds
composer run dev serves the whole app on FrankenPHP — including the prebuilt
admin SPA at /admin (served from public/; no separate build step). Open
http://127.0.0.1:8080.
Optional: Admin SPA hot-reload (HMR)
The admin SPA ships as a prebuilt bundle, so most apps need nothing extra. If you
are developing a custom Nuxt admin, run its dev server in a second terminal
alongside composer dev:
Set WAASEYAA_ADMIN_PATH (or extra.waaseyaa.admin_path in composer.json) to a
Nuxt admin package outside this skeleton if admin:dev cannot find one.
Configuration
config/waaseyaa.php— Framework configurationconfig/entity-types.php— Custom entity typesconfig/services.php— Service overrides
License
GPL-2.0-or-later
All versions of waaseyaa with dependencies
ext-sqlite3 Version *
php Version >=8.5
symfony/dotenv Version ^8.0
waaseyaa/framework Version ^0.1.0-alpha.273