Home > Article > Backend Development > How to replace framework entry files or application entry files with Lite files in thinkphp3.2_PHP Tutorial
How to replace framework entry files or application entry files with Lite files in thinkphp3.2_PHP Tutorial
- WBOYOriginal
- 2016-07-13 09:53:17761browse
How to replace the framework entry file or application entry file with Lite file in thinkphp3.2
This article describes the example of replacing the framework entry file or application entry file with Lite file in thinkphp3.2 method. Share it with everyone for your reference. The specific analysis is as follows:
Version 3.2 supports generating Lite files based on the current operating environment, which can replace the framework’s entry file or application entry file to improve operating efficiency.
Our suggestion is to generate Lite files after turning off debug mode in the production environment.
Note that currently the SAE platform does not support directly generating Lite files.
Generate Lite file
To generate a Lite file, you need to add constant definitions to the entry file:
The code is as follows:
define('BUILD_LITE_FILE',true);
By default, a lite.php file will be generated under the Runtime directory after running again.
If you need to modify the location or name of the Lite file, you can add the following configuration in the application configuration file:
The code is as follows:
'RUNTIME_LITE_FILE'=> APP_PATH.'lite.php'
After configuration, the location of the generated Lite file is APP_PATH.'lite.php'.
The content of the compiled file of the Lite file is the system default. If you want to change or add other compiled files, you can define the compiled list file externally. For example: We add the lite.php definition under the application configuration directory as follows:
?
|
return array( THINK_PATH.'Common/functions.php', COMMON_PATH.'Common/function.php', CORE_PATH . 'Think'.EXT, CORE_PATH . 'Hook'.EXT, CORE_PATH . 'App'.EXT, CORE_PATH . 'Dispatcher'.EXT, CORE_PATH . 'Model'.EXT, CORE_PATH . 'Log'.EXT, CORE_PATH . 'Log/Driver/File'.EXT, CORE_PATH . 'Route'.EXT, CORE_PATH . 'Controller'.EXT, CORE_PATH . 'View'.EXT, CORE_PATH . 'Storage'.EXT, CORE_PATH . 'Storage/Driver/File'.EXT, CORE_PATH . 'Exception'.EXT, BEHAVIOR_PATH . 'ParseTemplateBehavior'.EXT, BEHAVIOR_PATH . 'ContentReplaceBehavior'.EXT, ); |
All files defined in the lite.php file will be included in the compilation cache of the Lite file. You can also modify the generated lite file.
If you modify the framework file, application functions and configuration files, you need to delete the Lite file and regenerate it.
Since cloud platforms such as SAE do not support file writing, direct generation of Lite files is not supported.
Replacement entrance
Lite files can be used to replace framework entry files or application entry files.
Replace the framework entry file
After the Lite file is generated, you can modify the framework entry file in the original application entry file as follows:
The code is as follows:
require './ThinkPHP/ThinkPHP.php';
Changed to:
The code is as follows:
require './Runtime/lite.php';
After replacing the Lite file, the application compilation cache is no longer needed.
Replace application entry file
If your entry file has no other code or logic, you can also directly access the lite.php file as the application’s entry file. Copy the lite.php file to the same directory as the application entry file, and rename it directly to index.php for normal access as before (the original application entry file can be backed up for use when regenerating the Lite file).
Note: If your environment or directory location changes, or if you change the core framework, application functions, configuration and other files, you need to regenerate the Lite file.
I hope this article will be helpful to everyone’s PHP programming based on the ThinkPHP framework.