Routing & middleware
Register GET, POST and resource routes; name them, group them under a prefix and attach middleware. Route parameters are passed to controller handlers after middleware runs.
OMNIOPHP / OPEN-SOURCE PHP FRAMEWORKRoutes. Records.
Routes. Records.
Background jobs.
One PHP foundation.
OmnioPHP brings routing, an Active Record ORM, templates, authentication, queues and caching into a PHP application framework.
Build a server-rendered application or a JSON API. Group routes behind middleware, persist records through models, and move slow work into queue workers. The source and a task-tracker tutorial show how those parts connect.
LANGUAGEPHP
PACKAGE MANAGEMENTComposer
LICENCE FAMILYGPL-3.0
DEVELOPED BYAnteomnio
WHY A SHARED FOUNDATION MATTERSBuild the rules
Build the rules
your business needs.
An application has recurring technical work and decisions that belong specifically to your business.
The included tutorial builds a task tracker: routes select controller methods, a migration creates the tasks table, an Active Record model persists tasks, and a controller returns JSON or renders a view.
Login middleware establishes the session. The task-list query filters records by user_id. Those are different checks: your application must also enforce ownership when updating or deleting an individual task.
INSIDE OMNIOPHPFrom the request
From the request
to the work behind it.
The repository documents routing, middleware, an Active Record ORM, migrations, templates, authentication, caching, queues and command-line tooling.
Read the component documentation ↗Models & migrations
Use Active Record create(), find(), save() and delete(), with a fluent query builder for filtering. Migrations describe schema changes; models support relationships and soft deletion.
Templates & responses
Render templates with layout inheritance and escaped output, or send JSON with a response status. The tutorial builds both a task list and its request handlers.
Authentication & sessions
The supplied authentication controller handles login and registration. Session-based auth middleware gates routes; the application defines which records that user may access.
Queues & caching
A database-backed queue supports delayed jobs and retries. Cache drivers include File, Redis, Memcached and APCu; use them for results you can safely reuse.
CLI & development tools
The console includes controller and model generators, migrations and queue workers. The repository also includes PHPUnit tests, static-analysis configuration and documentation.
FOLLOW THE INCLUDED TUTORIALA task tracker.
A task tracker.
From table to browser.
The repository includes an eight-part tutorial, covering setup, controllers, persistence, validation, views, authentication and testing. Use it to follow the framework through a small application.
THE APPLICATION RECORD
Task
- user_id
- Who the task belongs to
- title
- The work to be done
- completed
- A boolean, initially false
- timestamps
- When the record changes
CREATE THE TABLE
Generate a migration, define the task fields with the schema builder and run the migration.
STORE AND READ TASKS
Define a Task model, connect it to the database and use the controller to create records and return a filtered list.
ADD THE INTERFACE
Validate the submitted title, render a task list and attach the login middleware to the task routes.
FOLLOW A REQUEST THROUGH A TEST
The tutorial finishes with a feature test. The repository also tests route parameters, middleware short-circuiting and unmatched routes.
GETTING STARTEDUse the setup guide
Use the setup guide
that belongs to the code.
Use Composer to install the declared packages, configure the application and database, then run the project locally. For a PHP 8.5 deployment, check the extensions and resolved dependencies against that runtime.
Its package manifest installs dependencies under resources/vendor. Read that manifest as well as the README when reviewing the environment.
- Choose the source version.
Review the repository history and documentation together. Keep a record of the revision you evaluate.
- Prepare a local environment.
Follow its installation and configuration instructions, using development credentials and sample data.
- Trace the first request.
Locate the route, the application code and the response. Make a small change and confirm where it appears.
- Test your intended runtime.
Run the project checks and your representative feature on the PHP version and services you plan to deploy.
CHOOSING A FRAMEWORKThe team has to
The team has to
live with the choice.
Evaluate OmnioPHP when you want to inspect its approach and are prepared to maintain an application built on it. Familiar syntax is a starting point; it does not settle the choice.
For an existing system, weigh the cost of adopting a new framework against improving the current application. A rewrite needs a reason tied to the work the system must do.
Questions for the people maintaining it
- Can we follow an unfamiliar request without help from the original author?
- Do the integrations we need fit the framework and our deployment?
- Can we diagnose a failure and safely change the affected code?
- Who will review dependencies, test updates and own ongoing maintenance?
PRACTICAL QUESTIONSBefore it becomes
Before it becomes
your application foundation.
The repository is the source for current technical requirements. These answers explain how to approach the decision.
Does OmnioPHP have external dependencies?
Yes. Its Composer manifest declares third-party packages and extension requirements. Review the manifest and lock file for the version you plan to use; a unified framework still has dependencies to maintain.
Where can I check runtime requirements?
Read composer.json and the test workflow for your selected revision. The package constraint and the versions exercised in CI are separate information; use both when preparing your PHP 8.5 environment.
Can I use it for an API?
The project documents API routing and JSON responses. Evaluate a complete endpoint, including permissions, validation and failure behaviour, rather than judging only the successful response.
Which licence should I review?
The package manifest identifies GPL-3.0-or-later. Read the licence included with your chosen source version and consider its requirements for your intended use and distribution.
Can Anteomnio help with implementation?
Yes. We can discuss the application, integration or evaluation work you need and agree a separate scope. Tell us about the intended workflow, current environment and the team that will maintain it.
Start with the feature
your team needs.
Tell us what the application must do and who will use it. We can help assess the foundation and scope the work around it.