Replace the entry file in thinkphp3.2

This article mainly introduces the method of replacing the framework entry file or application entry file with the Lite file in thinkphp3.2, involving ThinkPHP related configuration skills. I hope to be helpful.

The specific analysis is as follows:

The 3.2 version 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 recommendation is to generate Lite files after turning off debug mode in the production environment.

Note that the current SAE platform does not support directly generating Lite files.

Generate Lite files

To generate Lite files, you need to add constant definitions to the entry file:

define('BUILD_LITE_FILE',true);

By default, after running again Generate a lite.php file under the Runtime directory.

If you need to modify the location or name of the Lite file, you can add the following configuration in the application configuration file:

'RUNTIME_LITE_FILE'=> APP_PATH.'lite.php'

After configuration, the location of the generated Lite file is APP_PATH.'lite.php '.

The compiled file content 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 lite.php under the application configuration directory and define it 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 Entry

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:

require './ThinkPHP/ThinkPHP.php';

Change to:

require './Runtime/lite.php';

After replacing the Lite file, the application compilation cache is no longer needed.

Replace the application entry file

If your entry file has no other code and 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.

Related recommendations:

Detailed explanation on the comparison between TP5 and TP3.X

Implementation method of saving templates to database in TP3.0 framework

TP3.1.x modification success and failure jump page Method introduction

The above is the detailed content of Replace the entry file in thinkphp3.2. For more information, please follow other related articles on the PHP Chinese website!