How to Use a PHP Modular MVC Framework to Simplify PHP Applications Using the Package upMVC: Pure PHP web development without other frameworks

Recommend this page to a friend!

Download

Info

Example

Demos

Files

Install with Composer

Download

Reputation

Support forum

Blog

Links

Last Updated		Ratings				Unique User Downloads		Download Rankings
2025-10-21 (4 hours ago)		Not enough user ratings				Total: 90 This week: 6		All time: 9,960 This week: 7

Version		License		PHP version		Categories
`upmvc` 1.0.3		Freely Distributable		8.2		Libraries, Design Patterns, PHP 8

Description

Author

Adrian M

This package provides a system for building MMVC(Modular MVC)--based PHP applications, offering a structured approach to development.

It provides base model, view, and controller classes that application developers can extend to implement model, view, and controller classes specific to the application.

The package also provides additional modules with model, view, and controller classes to implement everyday tasks that many applications need, for instance:

- User authentication

- Email delivery

- User interface rendering using React.js

- User management

A module can take various forms, including a Single Page Application (SPA), a REACT app, TypeScript (TS), JavaScript (JS), or even an API module responding to requests across modules, eliminating the need for direct SQL queries if desired.

Adrian M

Performance

Level

Name:	Adrian M `<contact>`
Classes:	5 packages by Adrian M
Country:	Ireland
Age:	45
All time rank:	3840	4 in Ireland
Week rank:	7	1 in Ireland

Level 2

Instructions

Read - README.md

Example


<?php

/**

 * index.php - Application Entry Point

 * 

 * This is the main entry point for the upMVC framework.

 * All HTTP requests are routed through this file via .htaccess.

 * 

 * Bootstrap Sequence:

 * 1. Load Composer autoloader

 * 2. Instantiate Start class (triggers configuration and initialization)

 * 3. Execute upMVC() method (starts routing and middleware)

 * 

 * Requirements:

 * - PHP 8.0 or higher

 * - Composer dependencies installed (vendor/autoload.php)

 * - .env file configured in /etc directory

 * - .htaccess configured to route all requests to this file

 * 

 * @package upMVC

 * @author BitsHost

 * @copyright 2023 BitsHost

 * @license MIT License

 * @link https://bitshost.biz/

 * @created Tue Oct 31 2023

 */



// ========================================

// Load Dependencies

// ========================================



require_once 'vendor/autoload.php';



use upMVC\Start;



// ========================================

// Start Application

// ========================================



/**

 * Initialize and start the upMVC application

 * 

 * The Start constructor handles:

 * - Configuration loading from .env

 * - Error handler registration

 * - Request initialization

 * 

 * The upMVC() method handles:

 * - Router setup

 * - Middleware registration

 * - Route dispatching

 */

$fireUpMVC = new Start();

$fireUpMVC->upMVC();

Details

? upMVC noFramework v1.0.3 - Complete Documentation

> Modern, lightweight PHP noframework for rapid development with clean architecture

Status: ? Production Ready | PHP 8.1+ | PSR-4 Compliant | MIT License

? NEW: Modern UI System

upMVC v1.0.3 introduces a contemporary design system while maintaining complete backward compatibility:

? Modern BaseView: Contemporary CSS Grid/Flexbox layouts with dark mode
? Responsive Design: Mobile-first approach with modern navigation
? Alpine.js Integration: Lightweight interactivity (~40KB vs 87KB jQuery)
? Zero Breaking Changes: Drop-in replacement for existing BaseView

Quick Demo: /test (original) vs /test/modern (new design) Documentation: Modern BaseView Guide | Demo Instructions

? What is upMVC?

A lightweight, modern PHP 8.1+ noFramework built on Modular MVC (MMVC) architecture. Designed for developers who want flexibility without noFramework bloat. Features true modularity, "PHP Islands" for frontend integration (React/Vue), dependency injection, middleware pipeline, and clean routing. No forced conventions - use pure PHP or integrate modern JS noFrameworks as needed. Perfect for rapid development while maintaining performance and flexibility.

? Key Features: Modular architecture ? PHP 8.1+ ? PSR-4 compliant ? Dependency injection ? Middleware support ? Frontend noFramework integration ? Minimal learning curve

> ? Note: Included modules (admin, email, auth, react, etc.) are reference implementations showing different approaches to common problems. After installation, you can delete any modules you don't need - keep only what serves your project. Each module demonstrates different techniques (middleware vs manual auth checks, cached routes, etc.) to help you choose your preferred approach. See Module Philosophy for details.

? Quick Navigation

? New to upMVC? Start Here:

? First Steps Guide - Get running in 5 minutes
? How-To Guide - Complete development guide
? FAQ - Common questions and solutions
? Documentation Index - Complete documentation map

? Architecture & Philosophy:

? Pure PHP Philosophy - The upMVC NoFramework approach
? Module Philosophy - Modules as reference implementations
?? Islands Architecture - NEW! Complete guide to PHP + React Islands
?? React Integration Patterns - Five ways to integrate React/Vue/Preact
? ReactHMR - Hot Module Reload - Auto-reload without webpack
? Architectural Strengths - What makes upMVC powerful
? Routing Capabilities - Understanding the routing system
? URL Handling Explained - Request flow and middleware

? Bug Fixes & Improvements:

? Authentication Redirect Fix - Session intended_url handling
?? Assignment Operator Fix - Comparison vs assignment
? Missing Exit Statements - Proper redirect handling
? Output Before Header Fix - Header redirect timing
? Trailing Slash Fix - URL normalization
? Debug Code Cleanup - Production-ready code

? Verification & Release:

? Pre-Release Verification - Complete verification report
? Ready for Main - Production readiness checklist
? Verification Checklist - Step-by-step validation
? Enhancements - Latest improvements

? Development:

? /zbug Folder - Debug files and development utilities (excluded from Git)

Demo: https://upmvc.com/demo/

Rasmus Lerdorf: PHP NoFrameworks all suck!

<a href = "https://www.youtube.com/watch?v=DuB6UjEsY_Y&ab_channel=matperino" target="_blank">Rasmus Lerdorf: PHP NoFrameworks all suck!</a>

Use cases:

You can use the system as a standalone, as a library, as a library in the standalone version where it can be a module, you can also use it as a standalone in the standalone version /shop /blog /app /anything else - in this way, you split your app into multiple apps(shop, blog, app, anything else as separate instances of upMVC) each with their modules connected to the same or different endpoints.

? Installation

Option 1: Install as a Library

Add upMVC to your existing project:

composer require bitshost/upmvc

Post-installation steps: - Copy index.php from vendor to your project root - Add .htaccess rules for routing - Configure: /etc/Config.php, /etc/ConfigDatabase.php, /modules/mail/MailController.php

Option 2: Install as a Standalone Project

Create a new upMVC project:

# Install in new directory
composer create-project bitshost/upmvc yourProjectName

# Or install in current directory
composer create-project bitshost/upmvc .

After installation:

# Update autoloader when adding new modules
composer dump-autoload

# Update dependencies
composer update

?? Configuration

Edit these files with your project settings:

/etc/Config.php - Base URL, site paths, environment settings
/etc/ConfigDatabase.php - Database connection parameters
/modules/mail/MailController.php - PHPMailer SMTP configuration

?? Routing System

upMVC offers flexible routing at multiple levels:

Global Routes ? `/etc/Routes.php` - Application-wide routes
Module Routes ? `/modules/yourmodule/routes/Routes.php` - Module-specific routes
Module Initialization ? `/etc/InitMods.php` - Register module routes
Namespace Registration ? `composer.json` - Add PSR-4 autoload entries

"autoload": {
    "psr-4": {
        "YourModule\\": "modules/yourmodule/"
    }
}

After adding namespaces: Run composer dump-autoload

Quick Start: Add Your Module Routes

Create your routes file: `/modules/yourmodule/routes/Routes.php`
Define your routes using `$this->addRoute()` method
Register in `/etc/InitMods.php`: `$initRoutes->yourmodule();`
That's it - upMVC handles the rest automatically

Example: See /modules/test/routes/Routes.php for reference implementation

Note:

A friendly URL is a short and simple web address that redirects to a longer web address. Friendly URLs are called Aliases in Sitecore.

We achieve this by combining some .htacces rules with module routes. Check modules/test/routes/Routes.php and the .htaccess file - you will notice the rules established in the.htaccess file for these specific routes - you may build as many as you like.

In the same file, modules/test/routes/Routes.php, you will see for demonstration purposes how you may handle a large number of URLs with parameters (such as an idProduct) in a very straightforward way.

Steps

- Edit /etc/Config.php, /etc/ConfigDatabase.php, /modules/mail/MailController.php with your data. - Make your module in the MVC style (model, view, controller). - You may or may not wish to utilize BASE MODEL, BASE VIEW and BASE CONTROLLER from the common/bmvc subdirectory. - BaseModel contains all of the data required for CRUD OPERATIONS; simply expand it in your module model and you have a CRUD ready-made module; see example module modules/user. - Make a distinctive namespace for each module - Your module routes should be kept under modules/YourModule/routes - file Routes.php - Because these routes should be presented to Router, you must provide their namespace to InitMods.php and initialize your module routes. - Don't forget to update composer.json with your new namespaces for your module and routes, as well as refresh composer from the terminal: - composer dump-autoload - php composer.phar dump-autolad - setup your PHPMailer - mail/MailController.php

You have more than one method of accomplishing things in example modules, upMVC - don't enforce RULES like others do, but respect architecture models MVC, MMVC, and pure PHP and OOP programming rules.

The Names Convention

Considering recommendations:

- Model, View, Controller - will be called without using module name in their name. For example, module name = books: - Model.php - class Model; View.php - class View; Controller.php - class Controller; - and make a distinctive namespace for each module - namespace Modulename - e.g. Books; - Your module routes should be kept under modules/yourmodule/routes - file Routes.php: - Routes.php class Routes in folder /modules/books/routes - namespace Modulename\Routes, e.g. Books\Routes

The provided modules (Mail and Authentication) are for illustrative purposes only. You can safely delete them, as well as any other existing modules. The goal is to demonstrate the modularity of the system and how you can create your own custom modules to suit your specific project needs.

Diagram: upMVC-Diagram

File Structure:

upMVC-FileStructure

"Many noFrameworks may look very appealing at first glance because they seem to reduce web application development to a couple of trivial steps leading to some code generation and often automatic schema detection, but these same shortcuts are likely to be your bottlenecks as well since they achieve this simplicity by sacrifizing flexibility and performance."

<a href="https://toys.lerdorf.com/the-no-framework-php-mvc-framework" target="_blank">All NoFramweworks: "achieve this simplicity by sacrifizing flexibility and performance" Rasmus Lerdorf</a>

upMVC - MMVC, PHP MVC with modules. Modular MVC(Model, View, Controller) derive from Hierarchical Model?View?Controller (HMVC).

Introducing MODULAR MVC - Empowering Your Development

In the realm of modern noFrameworks, it often feels like they do everything except what truly matters. These noFrameworks tend to add layers of abstraction that demand you to learn new skills and pathways whenever you decide to switch. They also tend to clutter themselves with superfluous options, solving simple problems in needlessly convoluted ways.

Consider PHP, including its blade templating engine. Why introduce yet another template engine when PHP is already equipped for the task? Delving into a new noFramework often necessitates a substantial relearning effort, pushing you far beyond your existing PHP knowledge.

So, why should you choose MMVC?

MMVC, standing for Modular Model View Controller, is not about reinventing the wheel. Instead, it's about optimizing the use of exceptional components. It offers a structured, straightforward approach, and its versatility proves invaluable for project management and development.

But why MMVC specifically?

Modularity: MMVC allows you to work on a module without impacting the rest of your project. Modules can be interchanged and integrated seamlessly, enhancing your development agility.
Language Freedom: Perhaps most importantly, you have the freedom to write your modules in your preferred language, whether it's PHP, JS, PYTHON, or modern technologies like TS, React, Vue, Preact. There are no constraints on your creativity.
Development-Centric: MMVC was designed with development in mind. You can steer your project in any direction you desire, utilizing your own autoloader or composer autoload. Composer/packagist usage is optional, not obligatory.
"Islands" of Interactivity: Within this PHP-generated HTML, you strategically place interactive components built with noFrameworks like React, Vue, Preact or Svelte. These components handle dynamic elements, such as user interactions, real-time updates, and animations. Read here: <a href="https://upmvc.com/Blog/The-Rise-of-%22PHP-Islands%22:-A-Hybrid-Approach-to-Web-Development/#wbb1" target="_blank">The Rise of "PHP Islands": A Hybrid Approach to Web Development</a>

What truly sets MMVC apart is its ability to harness the latest PHP capabilities without constraint. No more endless loops, as this noFramework liberates your development possibilities.

BitsHost Team

upMVC DEMO

Open in a separate window

Files (480)

File	Role	Description
`common` (2 files, 3 directories)
`docs` (47 files, 2 directories)
`etc` (14 files, 7 directories)
`modules` (16 directories)
`tools` (1 file, 4 directories)
`vendor` (1 file, 2 directories)
`.htaccess`	Data	Auxiliary data
`composer.json`	Data	Auxiliary data
`composer.lock`	Data	Auxiliary data
`composer.phar`	Data	Auxiliary data
`index.php`	Example	Example script
`LICENSE`	Lic.	License text
`PROGRESS.md`	Data	Auxiliary data
`README.md`	Doc.	Documentation

File	Role	Description
`assets` (2 files)
`bmvc` (7 files)
`errors` (3 files)
`404.php`	Aux.	Auxiliary script
`500.php`	Aux.	Configuration script

File	Role	Description
`CommonCss.php`	Class	Class source
`ModernCss.php`	Class	Class source

File	Role	Description
`BaseController.php`	Class	Class source
`BaseControllerOrm.php`	Class	Class source
`BaseModel.php`	Class	Class source
`BaseModelOrm.php`	Class	Class source
`BaseView.php`	Class	Class source
`BaseViewModern.php`	Class	Class source
`ModernCss.php`	Class	Class source

File	Role	Description
`403.php`	Aux.	Configuration script
`404.php`	Aux.	Configuration script
`500.php`	Aux.	Configuration script

File	Role	Description
`examples` (4 files)
`routing` (3 files, 1 directory)
`APP_URL_VS_DOMAIN_NAME_ANALYSIS.md`	Data	Auxiliary data
`ARCHITECTURAL_STRENGTHS.md`	Example	Example script
`BUG_FIX_AUTH_ASSIGNMENT.md`	Data	Auxiliary data
`BUG_FIX_AUTH_REDIRECT.md`	Data	Auxiliary data
`BUG_FIX_MISSING_EXIT.md`	Data	Auxiliary data
`BUG_FIX_OUTPUT_BEFORE_HEADER.md`	Example	Example script
`BUG_FIX_TRAILING_SLASH.md`	Class	Class source
`CLEANUP_DEBUG_CODE.md`	Data	Auxiliary data
`CLEANUP_DUPLICATE_CONFIGS.md`	Data	Auxiliary data
`COMPONENT_LIBRARY.md`	Class	Class source
`CONFIG_CUSTOMIZATION_GUIDE.md`	Data	Auxiliary data
`CONFIG_QUICK_EDIT.md`	Class	Class source
`CONFIG_SIMPLE_EXPLANATION.md`	Data	Auxiliary data
`DOCUMENTATION-INDEX.md`	Data	Auxiliary data
`DOTENV_USAGE_EXAMPLES.md`	Class	Class source
`ENHANCEMENTS.md`	Data	Auxiliary data
`FAQ.md`	Data	Auxiliary data
`FIRST-STEPS-GUIDE.md`	Class	Class source
`GET_SET_USAGE_ANALYSIS.md`	Data	Auxiliary data
`HOW-TO-GUIDE.md`	Class	Class source
`ISLANDS_ARCHITECTURE.md`	Class	Class source
`ISLANDS_ARCHITECTURE_INDEX.md`	Data	Auxiliary data
`ISLANDS_DOCUMENTATION_SUMMARY.md`	Data	Auxiliary data
`MODULE_PHILOSOPHY.md`	Data	Auxiliary data
`MODULE_PHILOSOPHY_UPDATE.md`	Data	Auxiliary data
`PHILOSOPHY_PURE_PHP.md`	Data	Auxiliary data
`PRE_RELEASE_VERIFICATION.md`	Class	Class source
`PROTECTED_ROUTES_IMPLEMENTED.md`	Data	Auxiliary data
`PROTECTED_ROUTES_SOLUTION.md`	Class	Class source
`REACTHMR_COMPLETE.md`	Data	Auxiliary data
`REACTHMR_IMPLEMENTATION.md`	Example	Example script
`REACTHMR_QUICK_SUMMARY.md`	Example	Example script
`REACTHMR_VISUAL_GUIDE.md`	Data	Auxiliary data
`REACT_DOCUMENTATION_COMPLETE.md`	Data	Auxiliary data
`REACT_INTEGRATION_PATTERNS.md`	Class	Class source
`REACT_PATTERNS_SUMMARY.md`	Data	Auxiliary data
`REACT_QUICK_REFERENCE.md`	Data	Auxiliary data
`README.md`	Doc.	Documentation
`READY_FOR_MAIN.md`	Data	Auxiliary data
`ROUTING_CAPABILITIES.md`	Data	Auxiliary data
`ROUTING_STRATEGIES.md`	Class	Class source
`STATE_MANAGEMENT.md`	Data	Auxiliary data
`THE_FALLBACK_DISCOVERY.md`	Data	Auxiliary data
`UNDERSTANDING_CONFIG_ARRAY.md`	Data	Auxiliary data
`URL_HANDLING_EXPLAINED.md`	Data	Auxiliary data
`VERIFICATION_CHECKLIST.md`	Data	Auxiliary data
`WHY_CONSTANTS_VS_ENV.md`	Data	Auxiliary data

File	Role	Description
`CHART_ISLAND.md`	Class	Class source
`dotenv-quick-example.php`	Class	Class source
`FORM_ISLAND.md`	Class	Class source
`SEARCH_ISLAND.md`	Class	Class source

File	Role	Description
`examples` (5 files)
`ORGANIZATION_SUMMARY.md`	Data	Auxiliary data
`QUICK_REFERENCE.md`	Data	Auxiliary data
`README.md`	Doc.	Documentation

File	Role	Description
`Controller_WithCache.php`	Class	Class source
`Pattern_Tester.php`	Aux.	Configuration script
`Router_PatternMatching.php`	Class	Class source
`Router_PatternMatching_README.md`	Doc.	Documentation
`Routes_WithCache.php`	Class	Class source

File	Role	Description
`Cache` (3 files)
`Config` (2 files)
`Container` (2 files)
`Events` (2 files)
`Exceptions` (6 files)
`Middleware` (5 files)
`storage` (1 directory)
`.env`	Data	Auxiliary data
`Cache.php`	Class	Class source
`Config.php`	Class	Class source
`ConfigDatabase.php`	Class	Class source
`custom-routes.php`	Aux.	Configuration script
`Database.php`	Class	Class source
`ErrorHandler.php`	Class	Class source
`InitMods.php`	Class	Class source
`InitModsImproved.php`	Class	Class source
`Router.php`	Class	Class source
`Routes.php`	Class	Class source
`sample.sql`	Data	Auxiliary data
`Security.php`	Class	Class source
`Start.php`	Class	Class source

File	Role	Description
`CacheInterface.php`	Class	Class source
`CacheManager.php`	Class	Class source
`FileCache.php`	Class	Class source

File	Role	Description
`ConfigManager.php`	Class	Class source
`Environment.php`	Class	Class source

File	Role	Description
`Container.php`	Class	Class source
`ServiceProviderInterface.php`	Class	Class source

File	Role	Description
`Event.php`	Class	Class source
`EventDispatcher.php`	Class	Class source

File	Role	Description
`ConfigurationException.php`	Class	Class source
`DatabaseException.php`	Class	Class source
`ErrorHandler.php`	Class	Class source
`Exceptions.php`	Class	Class source
`RouteNotFoundException.php`	Class	Class source
`upMVCException.php`	Class	Class source

File	Role	Description
`AuthMiddleware.php`	Class	Class source
`CorsMiddleware.php`	Class	Class source
`LoggingMiddleware.php`	Class	Class source
`MiddlewareInterface.php`	Class	Class source
`MiddlewareManager.php`	Class	Class source

File	Role	Description
`admin` (7 files, 1 directory)
`auth` (3 files, 1 directory)
`dashboardexample` (4 files, 3 directories)
`enhanced` (2 files, 1 directory)
`mail` (1 file, 2 directories)
`moda` (3 files, 2 directories)
`newmod` (3 files, 1 directory)
`react` (3 files, 2 directories)
`reactb` (3 files, 2 directories)
`reactcrud` (3 files, 2 directories)
`reacthmr` (4 files, 2 directories)
`reactnb` (3 files, 1 directory)
`test` (4 files, 1 directory)
`testitems` (3 files, 4 directories)
`user` (3 files, 2 directories)
`userorm` (3 files, 3 directories)

File	Role	Description
`routes` (2 files)
`CACHE_LOCATION_UPDATE.md`	Data	Auxiliary data
`CACHE_TESTING_GUIDE.md`	Data	Auxiliary data
`Controller.php`	Class	Class source
`Controllera.php`	Class	Class source
`Model.php`	Class	Class source
`README.md`	Doc.	Documentation
`View.php`	Class	Class source

File	Role	Description
`routes` (1 file)
`Controller.php`	Class	Class source
`Model.php`	Class	Class source
`View.php`	Class	Class source

File	Role	Description
`routes` (1 file)
`sql` (2 files)
`templates` (4 files, 1 directory)
`Controller.php`	Class	Class source
`Model.php`	Class	Class source
`README.md`	Doc.	Documentation
`View.php`	Class	Class source

File	Role	Description
`complete_schema.sql`	Data	Auxiliary data
`schema.sql`	Data	Auxiliary data

File	Role	Description
`layout` (2 files)
`dashboard.php`	Aux.	Configuration script
`login.php`	Aux.	Configuration script
`settings.php`	Aux.	Configuration script
`users.php`	Aux.	Configuration script

File	Role	Description
`footer.php`	Aux.	Configuration script
`header.php`	Aux.	Configuration script

File	Role	Description
`phpmailer` (7 files)
`routes` (1 file)
`MailController.php`	Class	Class source

File	Role	Description
`DSNConfigurator.php`	Class	Class source
`Exception.php`	Class	Class source
`OAuth.php`	Class	Class source
`OAuthTokenProvider.php`	Class	Class source
`PHPMailer.php`	Class	Class source
`POP3.php`	Class	Class source
`SMTP.php`	Class	Class source

File	Role	Description
`modules` (1 directory)
`routes` (1 file)
`Controller.php`	Class	Class source
`Model.php`	Class	Class source
`View.php`	Example	Example script

File	Role	Description
`etc` (2 files)
`routes` (1 file)
`Controller.php`	Class	Class source
`Model.php`	Class	Class source
`View.php`	Class	Class source

File	Role	Description
`component.js`	Data	Auxiliary data
`Component.php`	Class	Class source

File	Role	Description
`etc` (1 directory)
`routes` (1 file)
`Controller.php`	Class	Class source
`Model.php`	Class	Class source
`View.php`	Class	Class source

File	Role	Description
`static` (2 directories)
`asset-manifest.json`	Data	Auxiliary data
`favicon.ico`	Data	Auxiliary data
`index.html`	Doc.	Documentation
`logo192.png`	Icon	Icon image
`logo512.png`	Data	Auxiliary data
`manifest.json`	Data	Auxiliary data
`robots.txt`	Doc.	Documentation

File	Role	Description
`main.f855e6bc.css`	Data	Auxiliary data
`main.f855e6bc.css.map`	Data	Auxiliary data