Download the PHP package lfphp/plite without Composer
On this page you can find all versions of the php package lfphp/plite. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
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 plite
PLite lightweight functional framework
lightweight, high-performance PHP development framework is implemented using functional methods . The framework integrates routing, controllers, configuration, static resource version control, reference event monitoring and triggering, and other capabilities to quickly implement a simple and lightweight web system. The framework uses namespace + constant prefix to protect the runtime from polluting other code bases and ensure code compatibility.
1. Installation
1.1 Manual Installation
Please clone the plité repository via git to download the latest version of the framework code:
Copy the code to the project code directory and import the startup file:
1.2 Installation via composer
Framework environment dependencies: a. PHP version ≥ 7.1 b. php ext-json extension c. lfphp/func function (automatically installed)
Install using Composer:
1.3 Installation via lfphp/pls
lfphp/pls is the plité installation script. The script includes multiple functions such as plité installation, project initialization, ORM generation, CRUD code generation, etc. It is recommended to use it.
Installation pls:
2. Basic usage
For basic usage of the framework, please refer to the code examples in the test/DemoProject directory.
2.1 Configuration File
Global Control Variables
Except for PLITE_APP_ROOT, which needs to be manually configured in the project, other PLITE_* constants have default values. The following lists only some important constants. If you need to know all constant definitions, you can refer to the framework code file: src/defines.php.
| Variable Name | Description | Default Value |
|---|---|---|
PLITE_APP_ROOT |
The project running root directory, other configuration file path logic is generally based on this directory extension. | Required |
PLITE_SITE_ROOT |
Site access URL path, such as: http://www.site.com/, of course, can be simplified to / absolute configuration. |
/ |
PLITE_CONFIG_PATH |
Configuration file directory, provided for use by the get_config() function. To distinguish it from other PHP files, it is generally named in the file.inc.php format. The configuration file uses the return syntax to return the configuration value. |
PLITE_APP_ROOT.'/config' |
PLITE_PAGE_PATH |
Template page directory, used by the include_page() function. |
PLITE_APP_ROOT.'/src/page' |
PLITE_PAGE_NO_FOUND |
404 page template | 404.php (placed under PLITE_PAGE_PATH) |
PLITE_PAGE_ERROR |
500 Site Error Page | 5xx.php (placed under PLITE_PAGE_PATH) |
Program Configuration
The framework's default configuration file directory is: PLITE_APP_ROOT + '/config', which can be reset by CONFIG_PATH.
The configuration file in this directory is named in the format of config_key.inc.php. The data returned by the configuration file can be obtained through the function get_config('config_key'), or the internal array sub-items can be directly obtained through the get_config('parent/child') method.
Example:
The framework requires the following configuration files by default:
routes.inc.phpprovides the website access routing tablestatic_version.inc.phpstatic resource version configuration information (always used ininclude_jsand other functions)
2.2 Routing System
2.2.1 Routing Configuration
The default parameter name in the URL is: r (can be reset by PLITE_ROUTER_KEY), and the default route is passed in queryString. For example: www.abc.com/?r=user/info&id=1.
The framework's routing configuration defaults to: routes.inc.php (can be reset via PLITE_ROUTER_CONFIG_FILE).
The route configuration syntax is:
2.2.2 Routing System Usage
2.2.3 Route Rewriting
Please refer to the routing rewrite rules description document.
2.3 Controller
There are no restrictions on framework controllers. Any class or method can be registered as a controller. Of course, it is recommended to design a project controller parent class during use to facilitate the processing of some unified behaviors (such as authentication, unified logging, etc.). The $_REQUEST parameter in the router will be passed as the first parameter to the action method.
2.4 Views
The framework supports the include_page function to introduce PHP template files.
The page directory defaults to: APP_ROOT+/src/page and can be reset by PLITE_PAGE_PATH.
Directions:
3. Framework runtime events
custom processing of key events by registering events event_register($event, $payload). The framework supports the following events:
| Event key | Event description | Callback function parameter description |
|---|---|---|
| EVENT_APP_START | The web program starts running (environment variables have been configured) | None |
| EVENT_APP_BEFORE_EXEC | Before controller execution | Parameter 1: hit controller (short name) Parameter 2: hit action (case insensitive) |
| EVENT_APP_EXECUTED | controller execution completed | Parameter 1: Execution result return parameter Parameter 2: Hit controller (abbreviation) Parameter 3: Hit action (case insensitive) |
| EVENT_APP_FINISHED | The web application has finished running | None |
| EVENT_APP_EXCEPTION | web program running abnormally | Parameter 1: Exception object Parameter 2: hit controller (abbreviation) Parameter 3: hit action (case insensitive) |
| EVENT_ROUTER_HIT | Route hit (web framework can execute code directly in route configuration without controller) | Parameter 1: hit route item (string, closure function, wildcard) |
| EVENT_ROUTER_URL | url() route generation function execution |
Parameter 1: generate url Parameter 2: input URI Parameter 3: input parameter array |
| EVENT_BEFORE_INCLUDE_PAGE | include_page() function execution starts (the default C/A execution result in web mode will include the page) |
Parameter 1: relative path of template file Parameter 2: input parameter array |
| EVENT_AFTER_INCLUDE_PAGE | include_page() function execution ends (the default C/A execution result in web mode will include the page) |
Parameter 1: template file absolute path Parameter 2: input parameter array |
4. Copyright Notice
The framework adopts the MIT copyright statement. Please abide by the copyright statement during use.
5. Others
The framework is only a lightweight routing framework. It is recommended to use it with the following frameworks when necessary:
① PORM PHP ORM library (lfphp/porm)
② Logger PHP log library (lfphp/logger)
③ Cache PHP cache library (lfphp/cache)
