本章我們將了解CakePHP中的環(huán)境變量、常規(guī)配置、數(shù)據(jù)庫(kù)配置和郵件配置。

配置 CakePHP 默認(rèn)自帶一個(gè)配置文件，我們可以根據(jù)自己的需要進(jìn)行修改。為此，有一個(gè)專用文件夾 “config”。 CakePHP 具有不同的配置選項(xiàng)。

讓我們從了解 CakePHP 中的環(huán)境變量開(kāi)始。

環(huán)境變量

環(huán)境變量使您的應(yīng)用程序在不同環(huán)境下的工作變得容易。例如，在開(kāi)發(fā)服務(wù)器、測(cè)試服務(wù)器、登臺(tái)服務(wù)器和生產(chǎn)服務(wù)器環(huán)境上。對(duì)于所有這些環(huán)境，您可以使用 env() 函數(shù) 讀取所需環(huán)境的配置并構(gòu)建您的應(yīng)用程序。

在您的 config 文件夾中，您將看到 config/.env.example。該文件包含將根據(jù)您的環(huán)境進(jìn)行更改的所有變量。首先，您可以在 config 文件夾中創(chuàng)建一個(gè)文件，即 config/.env 并定義這些變量并使用它們。如果您需要任何其他變量，可以將其放入該文件中。

您可以使用 env() 函數(shù)讀取環(huán)境變量，如下所示 -

示例

$debug = env('APP_DEBUG', false);

第一個(gè)是您想要的環(huán)境變量的名稱，第二個(gè)值是默認(rèn)值。如果沒(méi)有找到環(huán)境變量的值，則使用默認(rèn)值。

常規(guī)配置

下表描述了各種變量的作用以及它們?nèi)绾斡绊懩?CakePHP 應(yīng)用程序。

*/
   'Datasources' => [
      'default' => [
         'host' => 'localhost',
         'username' => 'my_app',
         'password' => 'secret',
         'database' => 'my_app',
         'url' => env('DATABASE_URL', null),
      ],
      /*
         * The test connection is used during the test suite.
      */
      'test' => [
         'host' => 'localhost',
         //'port' => 'non_standard_port_number',
         'username' => 'my_app',
         'password' => 'secret',
         'database' => 'test_myapp',
         //'schema' => 'myapp',
      ],
   ],

config/app.php

'Datasources' => [
   'default' => [
      'className' => Connection::class,
      'driver' => Mysql::class,
      'persistent' => false,
      'timezone' => 'UTC',
      //'encoding' => 'utf8mb4',
      'flags' => [],
      'cacheMetadata' => true,
      'log' => false,
      'quoteIdentifiers' => false,
      //'init' => ['SET GLOBAL innodb_stats_on_metadata = 0'],
   ],
]   

Let us understand each parameter in detail in config/app.php.

Email Configuration

Email can be configured in file config/app.php. It is not required to define email configuration in config/app.php. Email can be used without it. Just use the respective methods to set all configurations separately or load an array of configs. Configuration for Email defaults is created using config() and configTransport().

Email Configuration Transport

By defining transports separately from delivery profiles, you can easily re-use transport configuration across multiple profiles. You can specify multiple configurations for production, development and testing. Each transport needs a className. Valid options are as follows ?

• Mail ? Send using PHP mail function

• Smtp ? Send using SMTP

• Debug ? Do not send the email, just return the result

You can add custom transports (or override existing transports) by adding the appropriate file to src/Mailer/Transport. Transports should be named YourTransport.php, where 'Your' is the name of the transport.

Following is the example of Email configuration transport.

'EmailTransport' => [
   'default' => [
      'className' => 'Mail',
      // The following keys are used in SMTP transports
      'host' => 'localhost',
      'port' => 25,
      'timeout' => 30,
      'username' => 'user',
      'password' => 'secret',
      'client' => null,
      'tls' => null,
      'url' => env('EMAIL_TRANSPORT_DEFAULT_URL', null),
   ],
],

Email Delivery Profiles

Delivery profiles allow you to predefine various properties about email messages from your application, and give the settings a name. This saves duplication across your application and makes maintenance and development easier. Each profile accepts a number of keys.

Following is an example of Email delivery profiles.

'Email' => [
   'default' => [
   
      'transport' => 'default',
      'from' => 'you@localhost',
   ],
],