Home > Article > Backend Development > What are the thinkphp configuration types? How to achieve it?
1. What are the configuration types of thinkphp?
1. In thinkphp, there are 6 configurations. That is, conventional configuration, application configuration, extended configuration, module configuration, scene configuration, and dynamic configuration.
2. The conventional configuration is the system default configuration.
3. Application configuration is the individual configuration of the application developed and created by ourselves.
4. Extension configuration is mainly to implement the configuration used by some extension programs during the development process of our project.
5. Module configuration is the configuration of each module in an application.
6. Scenario configuration is mainly to implement the configurations we set in different development environments. If we work at home, the computer environment may be different; if we work in a company, the company's computer environment may be different.
7. Dynamic configuration is developed and implemented in our module. For example, we define the database configuration in a controller.
2. What is the implementation principle of thinkphp configuration?
1. Thinkphp implements such different types of configurations, which to a large extent facilitates our modular configuration and enhances the flexibility of configuration.
2. The configuration loading order of thinkphp is mainly in the following order. Dynamic configuration》》Module configuration》》Extended configuration》》Application configuration》》Conventional configuration
3.thinkphp implements configuration mainly using PHP’s array_merage() function (if two or more If the array elements have the same key name, the last element will overwrite the other elements). When our system loads our configuration file, it will overwrite the previous configuration file, so the execution sequence of the second step above is achieved.
3. Why should we implement such a configuration?
1. Through different types of configurations, we facilitate project configuration management. If we join, we will use the configuration that comes with the framework. When we are developing a certain module and need to store data in the database of another server, our project will not be implemented. There are many situations like this, this is just a simple example.
4. Configuration file requirements
All configuration files use arrays. When our system loads the configuration file, it will return an array, and this array is ours. Configure the project. To access configuration items in the system, we can use the config() helper function or the config class
5. How to implement these types of configurations?
1. Conventional configuration.
The convention configuration is directly in convention.php under the core directory of the framework, and I won’t go into details here.
2. Application configuration.
When we create a project, the framework will create configuration files such as config.php and database.php in the application directory by default. We can operate directly in the corresponding file. The following separate explanation mainly uses creating a directory for configuration. The effect is the same, it is nothing more than changing the file path.
a. Define the configuration file path, find the project entry file, and create a config directory in the directory at the same level as the application (the subsequent configuration explanations are all operated under this directory, and will not be explained separately below).
define('CONF_PATH', __DIR__.'/../config/');Next, just create the configuration file directly under the directory. The name of the created file is not necessarily limited to config and database. As for the configuration items in the file, they are the same as the convention.php configuration file. When we run the project, the configuration items under this directory will be automatically loaded.
3. Extended configuration. The extended configuration is mainly the extended use of some data we use in development. For example, when we use email, it involves the account of the email. You can configure it under this directory. We create an extra directory under the config directory and create the corresponding files under this directory. For example, I created the email.php file below and defined the following content:
<?phpreturn ["user_emial" => "1005349393@qq.com"];
Load this configuration item in our system.
var_dump(config("email.user_emial")); // 在系统默认中，会给我们的环境变量都加一个PHP的前缀，并且都会将配置项转换为大写。这里我们使用我们的助手函数便可直接访问配置项。
4. Module configuration. Here is a brief explanation. The main thing is to create the corresponding config.php, database.php and other files under our module directory.
5. Scene configuration. ***This is the ultimate tip of this article. The scene configuration is mainly to adapt to our different development environments. For example, our environment at the company is inconsistent with the environment at home. At this time, we may need to modify many places, and at the same time we have to modify it again when we return to the company. Wouldn’t this be Very troublesome.
First, we load a configuration item in the configuration file under the config directory.
'app_status' => 'office', // 这里的配置项的值就是我们对应的配置环境。
接下来，在我们的config目录下面创建一个office.php（这里的文件名必须和上面配置项的值完全一致）
最后，我们直接在我们的office.php配置文件中配置即可。其实在thinkphp还有个比较不错的功能就是.env。之前一直知道laravel有，没主要thinkphp5，最近才发现。使用该功能对于开发中的配置又方便了很多了。很赞。
首先我们在我们的项目目录下面创建一个.env的文件，里面配置我们的配置项。如下
status= office
我们要使用的话，直接使用框架自带的env类即可。至于更多有关env的方法直接参考开发手册。
'app_status' => Env::get("status");我们将上一步场景配置项中的值设置为.env文件中的配置项。一定要引入ENV这个类。通过我们的.env文件，只需要我们实现将一些配置文件配置好，或者将一些常用的配置文件放在.env文件中，我们就只修改这一个文件即可。
6.动态配置。动态配置顾名思义是随着我们项目开发的需要来配置，而不是直接使用我们配置文件中的配置。下面列举一个简单的实例。
<?php
namespace app\index\controller;use think\Controller;class Index extends Controller
{public function index()
{
config("app_name", "weixin"); // 在控制器中配置一个app_name的配置项，这里也可以使用config类来操作。
}
}The above is the detailed content of What are the thinkphp configuration types? How to achieve it?. For more information, please follow other related articles on the PHP Chinese website!