Deploy an application using a code package

Online applications: Nginx with PHP-FPM

Application monitoring: ARMS

For SAE applications with PHP versions 5.4 to 7.3, you can enable application monitoring to obtain more detailed monitoring information, such as inter-application call chain tracing and resource access latency for ApsaraDB RDS for MySQL and Tair (Redis OSS-compatible).For more information, see the following documents:

• ARMS application monitoring overview

• Configure PHP application monitoring in SAE

Software versions

The following table describes the publicly available PHP environments. If you require a later version of the PHP environment, join the DingTalk group (ID: 32874633) and contact a product technical expert for assistance.

System directories

The SAE PHP environment uses the following default directories for package deployment:

The following table describes the default configurations of official PHP-FPM.

The following table describes the default configurations of official Nginx.

Built-in extensions

Related permissions

Official PHP-FPM and Nginx use the www-data user to run applications by default. The following table describes the permissions.

www-data www-data

www-data www-data

root root

drwxrwxrwx 2 root root 4096 May 13  2021 nginx
drwxrwxrwx 1 root root 4096 Apr  8 11:45 php

Official and PECL extensions

When you deploy an application, you can configure the php.ini file to enable built-in extensions, including official PHP extensions and PECL extensions. For more information, see Set the configuration file for a PHP application.

php -m

The following code provides sample outputs of the built-in extensions that are supported by different runtime environments:

[PHP Modules]
amqp
ARMS
bcmath
bz2
calendar
Core
ctype
curl
date
dom
exif
fileinfo
filter
ftp
gettext
gmp
hash
iconv
igbinary
imagick
json
libxml
mbstring
mcrypt
memcached
mongodb
msgpack
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
pdo_sqlite
Phar
posix
readline
redis
Reflection
session
shmop
SimpleXML
soap
sockets
sodium
SPL
sqlite3
standard
swoole
sysvmsg
sysvsem
sysvshm
timezonedb
tokenizer
xdebug
xml
xmlreader
xmlrpc
xmlwriter
yaml
Zend OPcache
zip
zlib

[Zend Modules]
Xdebug
Zend OPcache

[PHP Modules]
amqp
ARMS
bcmath
bz2
calendar
Core
ctype
curl
date
dom
exif
fileinfo
filter
ftp
gettext
gmp
hash
iconv
igbinary
imagick
json
libxml
mbstring
mcrypt
memcached
mongodb
msgpack
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
pdo_sqlite
Phar
posix
readline
redis
Reflection
session
shmop
SimpleXML
soap
sockets
sodium
SPL
sqlite3
standard
swoole
sysvmsg
sysvsem
sysvshm
timezonedb
tokenizer
xdebug
xml
xmlreader
xmlrpc
xmlwriter
yaml
Zend OPcache
zip
zlib

[Zend Modules]
Xdebug
Zend OPcache

[PHP Modules]
amqp
ARMS
bcmath
bz2
calendar
Core
ctype
curl
date
dom
exif
fileinfo
filter
ftp
gettext
gmp
hash
iconv
igbinary
imagick
json
libxml
mbstring
mcrypt
memcached
mongodb
msgpack
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
pdo_sqlite
Phar
posix
readline
redis
Reflection
session
shmop
SimpleXML
soap
sockets
sodium
SPL
sqlite3
standard
swoole
sysvmsg
sysvsem
sysvshm
timezonedb
tokenizer
xdebug
xml
xmlreader
xmlrpc
xmlwriter
yaml
Zend OPcache
zip
zlib

[Zend Modules]
Xdebug
Zend OPcache

[PHP Modules]
amqp
ARMS
bcmath
bz2
calendar
Core
ctype
curl
date
dom
exif
fileinfo
filter
ftp
gettext
gmp
hash
iconv
igbinary
imagick
json
libxml
mbstring
memcached
mongodb
msgpack
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
pdo_sqlite
Phar
posix
readline
redis
Reflection
session
shmop
SimpleXML
soap
sockets
sodium
SPL
sqlite3
standard
swoole
sysvmsg
sysvsem
sysvshm
timezonedb
tokenizer
xdebug
xml
xmlreader
xmlrpc
xmlwriter
yaml
Zend OPcache
zip
zlib

[Zend Modules]
Xdebug
Zend OPcache

[PHP Modules]
amqp
ARMS
bcmath
bz2
calendar
Core
ctype
curl
date
dom
exif
fileinfo
filter
ftp
gettext
gmp
hash
iconv
igbinary
imagick
json
libxml
mbstring
memcached
mongodb
msgpack
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
pdo_sqlite
Phar
posix
readline
redis
Reflection
session
shmop
SimpleXML
soap
sockets
sodium
SPL
sqlite3
standard
swoole
sysvmsg
sysvsem
sysvshm
timezonedb
tokenizer
xdebug
xml
xmlreader
xmlrpc
xmlwriter
yaml
Zend OPcache
zip
zlib

[Zend Modules]
Xdebug
Zend OPcache

[PHP Modules]
amqp
ARMS
bcmath
bz2
calendar
Core
ctype
curl
date
dom
exif
fileinfo
filter
ftp
gettext
gmp
hash
iconv
igbinary
imagick
json
libxml
mbstring
memcached
mongodb
msgpack
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
pdo_sqlite
Phar
posix
readline
redis
Reflection
session
shmop
SimpleXML
soap
sockets
sodium
SPL
sqlite3
standard
swoole
sysvmsg
sysvsem
sysvshm
timezonedb
tokenizer
xdebug
xml
xmlreader
xmlrpc
xmlwriter
yaml
Zend OPcache
zip
zlib

[Zend Modules]
Xdebug
Zend OPcache

[PHP Modules]
amqp
ARMS
bcmath
bz2
calendar
Core
ctype
curl
date
dom
ereg
exif
fileinfo
filter
ftp
gettext
gmp
hash
iconv
igbinary
imagick
json
libxml
mbstring
memcached
mongodb
msgpack
mysqli
mysqlnd
openssl
pcntl
pcre
PDO
pdo_mysql
pdo_sqlite
Phar
posix
readline
recode
redis
Reflection
session
shmop
SimpleXML
soap
sockets
SPL
sqlite3
standard
swoole
sysvmsg
sysvsem
sysvshm
timezonedb
tokenizer
xdebug
xml
xmlreader
xmlrpc
xmlwriter
yaml
zip
zlib

[Zend Modules]
Xdebug

Install extensions using the console and API

You can enable official PHP extensions or install specific versions of PECL extensions using the SAE console or by calling an API. For more information, see Deploy a PHP application.

Install third-party extensions

This section provides an example of how to install a third-party extension. The example shows how to install the YAML extension by compiling its source code in a PHP-FPM 7.3 environment.

1. Create an SAE application that uses PHP 7.3 as the runtime environment.

2. Enable public network access. For more information, see Configure a NAT gateway to allow an SAE application to access the Internet.

3. Log on to the instance using the Webshell and run the following commands to install and compile the extension.

   # Obtain the source code.
   wget https://pecl.php.net/get/yaml-2.2.2.tgz
   tar -zxvf yaml-2.2.2.tgz
   # Compile and install the extension.
   cd yaml-2.2.2 && \
   phpize && \
   ./configure && \
   make && make install

4. Download the extension to your local machine. For more information, see Use logs to upload and download files for application diagnosis.

   The extension is stored in the following path:

   /home/admin/yaml-2.2.2/modules/yaml.so

5. Package the extension into a ZIP package. The following code shows the structure of the ZIP package:

   .
   ├── nginx
   │ ├── default.conf
   │ ├── fastcgi_params
   │ ├── global
   │ └── root.dir
   ├── php
   │ ├── index.php
   └── extensions
    └── yaml.so

6. Deploy the application, upload the new ZIP package, and add a php.ini configuration to enable the extension.

   extension=/home/admin/app/extensions/yaml.so

7. Log on to the instance using the Webshell and check whether the extension is loaded.

   # php -m | grep yaml
   yaml

Default service ports

The following table describes the default service port values of the Nginx and PHP-FPM programs that are configured in SAE.

PHP-FPM logs: standard output

• By default, PHP-FPM logs are output to real-time logs. The following code shows the configuration. The configuration file path is /usr/local/etc/php-fpm.d/docker.conf.

  [global]
  error_log = /proc/self/fd/2
  log_limit = 8192
  
  [www]
  access.log = /proc/self/fd/2

• By default, PHP error logs are not configured to be displayed. The following code shows the configuration from the php.ini file:

  error_log => no value => no value
  log_errors => Off => Off
  log_errors_max_len => 1024 => 1024

• To output error logs to real-time logs, configure the php.ini file with the following setting when you create or deploy the application:

  log_errors = on
  error_log = /proc/self/fd/2

Nginx logs: standard output

• By default, Nginx logs are output to real-time logs. The following code shows the configuration. The configuration file path is ./nginx/default.conf.

  #access_log /dev/stdout;
  error_log stderr;

• You can enable access_log. By default, the logs are output to real-time logs.

File cache: static files, images, and media

; Enable OPcache
opcache.enable=1
; Disable OPcache
;opcache.enable=0

File cache: PHP code

For static files, such as images, videos, CSS, and JS, you can enable or disable Nginx static file caching. For more information about the configuration, see the Demo and Module ngx_http_headers_module.

• Enable static resource caching: This is suitable for scenarios such as online services and sites with many media files. This improves throughput capacity and reduces read IOPS.

• Disable static resource caching: This is suitable for scenarios such as remote debugging, uploads, and downloads. This lets you access files in real time.

    # Static resource cache
    location ~* \.(?:jpg|jpeg|gif|png|ico|cur|gz|svg|svgz|mp4|ogg|ogv|webm|htc)$ {
        # Disable cache
        #expires off;
        # Enable cache
        expires 1s;
    }

Hot restart services

• You can use a ConfigMap to dynamically configure and modify file content.

• You can use the Webshell to dynamically restart services.

  • Hot restart Nginx (without service interruption)

    # Test the validity of the configuration file.
    nginx -t
    # Dynamically restart the service.
    nginx -s reload

  • Hot restart PHP-FPM (This may cause a stream interruption. You need to check the php.ini configuration.)

    ps uax | grep 'php-fpm: master' | grep -v grep | awk '{print $2}' | xargs kill -USR2

Upload and download

SAE supports multiple methods for uploading and downloading files. Select a method as needed:

• Console: Upload and download small files for debugging (The file size cannot exceed 10 MB).

  You can upload and download files from the SAE console. For more information, see Use the Webshell to upload and download files.

• Console: remote debugging.

• Persistent storage: NAS or OSS.

  • When you deploy an application, you can mount NAS or OSS to share a file directory.

  • Upload and download files to or from NAS using Serverless Devs.

  • Upload and download files to or from OSS using the OSS console.

  • Upload and download files to or from OSS using ossutil.