PHPackages celeris/mvc - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Framework](/categories/framework) 4. / 5. celeris/mvc ActiveProject[Framework](/categories/framework) celeris/mvc =========== Celeris MVC base application scaffold for building server-rendered web applications. 1.0.0(1mo ago)02MITPHPPHP >=8.4 Since May 8Pushed 1mo agoCompare [ Source](https://github.com/jgarcias-cr/celeris-mvc)[ Packagist](https://packagist.org/packages/celeris/mvc)[ RSS](/packages/celeris-mvc/feed)WikiDiscussions main Synced 1w ago READMEChangelogDependencies (1)Versions (2)Used By (0) Celeris MVC Stub ================ [](#celeris-mvc-stub) `celeris/mvc` is a base application scaffold for building server-rendered web applications on top of `celeris/framework`. It is designed to help you start with a working MVC structure instead of a blank project: controllers, views, services, repositories, configuration, asset build hooks, example CRUD pages, and optional integrations are already in place. What It Is For -------------- [](#what-it-is-for) Use this package when you want to build a traditional web application with HTML pages rendered on the server. It is a good fit for: - internal dashboards - admin panels - business applications with forms and CRUD flows - projects that prefer server-rendered pages over SPA-heavy architecture - teams that want clean MVC structure without a large framework footprint Included Features ----------------- [](#included-features) - Server-rendered application bootstrap with a working homepage and contacts CRUD flow - Attribute-based controller routing - MVC layering with controllers, services, repositories, and models already separated - Form request objects and model policies for explicit validation and authorization - Multiple view engine options with configuration for `php`, `twig`, `plates`, and `latte` - Shared layouts and partials for starter UI composition - Vite-based asset pipeline for Alpine.js, CSS, and static images - Database-backed or file-backed contacts storage depending on configuration - Autodiscovered model lifecycle listeners for `onCreate`, `onUpdate`, `onDelete`, and `onShow` - Environment-based security toggles for JWT, opaque tokens, cookie sessions, API tokens, mTLS, and CSRF - Built-in request throttling configuration - Optional notification integrations for SMTP, in-app notifications, transactional outbox, realtime delivery, and dispatch workers - CLI wrapper for Celeris commands plus a template smoke-test script Advantages ---------- [](#advantages) - Faster delivery: you can start from a functioning web app instead of assembling the basics manually - Flexible rendering: choose the template engine that best fits your team without rewriting the scaffold - Clean extension points: generated base classes let you customize application code while keeping scaffolding boundaries clear - Practical defaults: forms, layouts, views, and CRUD pages help teams move from scaffold to real feature work quickly - Good migration path: the stub begins simple, but leaves room for database-backed workflows, notifications, and stronger security as the app grows Default Application Surface --------------------------- [](#default-application-surface) The scaffold currently includes: - a homepage route with a starter welcome screen - a contacts section with list, detail, create, edit, and delete pages - shared layout and partial templates - example middleware hook points for protected routes - configurable rendering through the selected view engine Model lifecycle listeners live under `app/Listeners/Models` and are registered automatically by `AppServiceProvider`. The sample contacts domain is intentionally small. It exists to demonstrate the structure and request flow, not to define how your real application should look. Quick Start ----------- [](#quick-start) Create a project from the package: ``` composer create-project celeris/mvc my-app cd my-app cp .env.example .env composer install php celeris app-key npm install npm run build php -S 127.0.0.1:8000 -t public ``` If you are working inside the Celeris monorepo, the scaffold can also fall back to the local framework bootstrap and CLI binary during development. View Engines ------------ [](#view-engines) The default view engine is plain PHP templates, which keeps the initial setup light. If your team prefers another renderer, the scaffold is already prepared for: - `twig/twig` - `league/plates` - `latte/latte` Switching engines is controlled through `VIEW_ENGINE` and the related view configuration in `.env`. To validate template rendering, you can use: ``` php scripts/view-smoke.php php scripts/view-smoke.php --all ``` Frontend Assets --------------- [](#frontend-assets) The package includes a Vite-based asset pipeline for Alpine.js, CSS, and static images. Useful commands: ``` npm run build npm run dev npm run watch ``` Compiled assets are written under `public/assets`. Alpine.js --------- [](#alpinejs) `resources/js/app.js` is the default frontend entrypoint and boots Alpine.js for the stub. The sample contacts pages use Alpine for: - client-side pagination - delete confirmation before form submission - lightweight UI state without introducing a SPA runtime The intended pattern is server-rendered HTML first, with Alpine directives layered onto the specific fragments that need interactivity. Project Structure ----------------- [](#project-structure) - `public/index.php` boots the HTTP kernel and loads route files - `routes/web.php` registers page controllers and browser routes - `routes/api.php` is ready for optional MVC/API hybrid routes - `app/Http/Controllers` contains page controllers - `app/Http/Requests` contains form request classes with `authorize()` and `rules()` - `app/Services` holds application use cases - `app/Repositories` contains persistence-facing code - `app/Models` contains view-facing domain models - `app/Policies` contains model action policies such as `view`, `create`, `update`, and `delete` - `app/Views` contains layouts, partials, and page templates - `config` centralizes app, view, database, and security behavior - `database/migrations` and `database/seeds` contain starter persistence files - `resources` contains source frontend assets - `scripts` contains helper scripts such as the renderer smoke test - `vite.config.js` defines the frontend build output for `public/assets` Storage and Data ---------------- [](#storage-and-data) The contacts example can work with database-backed persistence or a simpler file-backed mode, depending on your environment configuration. That makes the scaffold useful both for quick local prototypes and for real applications that will move into managed database infrastructure. Recommendations --------------- [](#recommendations) - Replace the sample `Contact` domain early with your own domain language and workflows - Pick one template engine deliberately and remove unused ones if you want a tighter project surface - Review `.env.example` closely before deployment, especially security and view cache settings - Set `APP_KEY` before enabling signed cookies or other stateful security features - Keep CSRF enabled for form-based flows unless you have a strong reason not to - Use the sample CRUD pages as reference implementations, not as long-term placeholder UI - Add tests around your real controllers, templates, and form handling as soon as you begin customization Tip --- [](#tip) This stub works best when you treat it as a strong starting structure, not a finished product. Keep the layering, reuse the rendering and asset pipeline conventions, and let the sample pages guide your first production features rather than survive unchanged for too long. ### Health Score 41 — FairBetter than 87% of packages Maintenance94 Actively maintained with recent releases Popularity2 Limited adoption so far Community8 Small or concentrated contributor base Maturity51 Maturing project, gaining track record Bus Factor1 Top contributor holds 80.6% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Unknown Total 1 Last Release 32d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/90e28732274c3c892bed8cb648281ab3cabcae63cd06df439c6c0d703c097250?d=identicon)[jgarcias](/maintainers/jgarcias) --- Top Contributors [![jgarcias-cr](https://avatars.githubusercontent.com/u/202754121?v=4)](https://github.com/jgarcias-cr "jgarcias-cr (29 commits)")[![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4)](https://github.com/github-actions[bot] "github-actions[bot] (7 commits)") --- Tags frameworkmvcSkeletonstarterceleris ### Embed Badge ![Health badge](/badges/celeris-mvc/health.svg) ``` [![Health](https://phpackages.com/badges/celeris-mvc/health.svg)](https://phpackages.com/packages/celeris-mvc) ``` ### Alternatives [laminas/laminas-mvc-skeleton Laminas MVC Skeleton Application 18392.3k](/packages/laminas-laminas-mvc-skeleton) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)