Download the PHP package dspaccapeli/file-based-router without Composer
On this page you can find all versions of the php package dspaccapeli/file-based-router. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download dspaccapeli/file-based-router
More information about dspaccapeli/file-based-router
Files in dspaccapeli/file-based-router
Package file-based-router
Short Description Simple file-based router to easily serve your public endpoints from a directory.
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package file-based-router
File-based Router
Simple file-based router to automatically route requests to files in a directory
- Introduction
- Get started
- Usage
- Router code
Introduction
This File-based router is a simple routing system written in PHP that allows developers to easily handle URL routing in their PHP projects. It uses file-based routing rules to map URLs to specific controllers or functions, making it easy to add new routes and modify existing ones.
The router is lightweight, easy to set up and can work seamlessly with any PHP framework or CMS. It consists of a single routing functions of around 20 LOCs and can be understood in a couple of minutes.
This repo wraps the package to make it easily installable via Composer. If you want to use the function directly you can copy it in your source code directly. This readme file provides all the necessary information for installing, configuring and using the file-based router in your PHP project.
Get Started
First, install File-Based Router via the Composer package manager:
Then, to use it in your project, simply require the Composer autoloader and call the route function in your entrypoint (usually the index.php file):
If this is yout folder structure:
Then the $endpoints_abs_path variable should be set to __DIR__ . "/../controllers/".
Note on import scoping
If you want to access objects imported with require or import (I will use the terms interchangeably) in the entrypoint/index file from the controller files, you need to be careful about their scope.
Variables required in the entrypoint/index file are not available in the controller files. route is just a function that is called in the entrypoint/index file, normal scoping rules apply. Thus variables need to be re-required in the controller files as well. This is not true for functions, which will be available in the controller files.
I recommend to define the relevant imports and required objects in each controller file each time to be more explicit. It is better for maintainability, makes it clear what is available to the developers and helps some linting systems. In that case you can use the the require_once or import_once without worrying about the scope of the variables.
Note that this is only one way of doing it. There are multiple ways of solving the imports scoping, this is just one of them.
Usage
route parameters
> $url_path
It is the path of the URL to be routed. It must be a string.
> $controller_path
It is the absolute path to the directory containing the endpoints. It must be a string and defaults to the directory /var/www/html if not specified.
> $filter_function
It is a function that takes the $url_path as a parameter and returns a boolean. It can be used to filter out some URLs. It defaults to null if not specified.
If the function returns true on the $url_path, the router will call the $fallback_handler and return false.
I use it to filter out requests for the view files (.view.php), which are not meant to be called directly, but I leave co-located with the controller files for convenience.
> $fallback_handler
It is the function that is called if the file/endpoint does not exist. The default failure mode calls http_response_code(404) if not specified.
> $view_suffix
It is the suffix of the view files. It defaults to null if not specified. If it is set, the router will also include the view file corresponding to the requested URL.
After including the controller file, the router will look for a file with the same name as the controller file but with the suffix specified in $view_suffix and include it if it exists.
This is useful if you want to separate the controller logic from the view logic. The controller will not have to manually call the view file.
The variables defined in the controller will be available in the view file.
> $extension
It is the extension of the controller files. It defaults to .php if not specified.
route returns
If the routing is successful, the router will include the file corresponding to the requested URL and exit the script and return true.
If the routing fails, the router will return false and the script will continue to run.
Router code
The router is a single function of around 20 lines of code. It is very easy to understand and modify.
Feel free to copy-paste it in your project and modify it to suit your needs. Contribute to the project if you want to improve it.
This File-Based Router is an open-sourced software licensed under the MIT license.
Information about the software license under which the router is released, including any restrictions on use and distribution.
