laravel s下載 - laravel s源碼下載

英文文檔 | 中文文檔

LaravelS 是 Laravel/Lumen 和 Swoole 之間的開箱即用適配器

持續更新

請Watch此存儲庫以獲取最新更新。

特徵
基準
要求
安裝
跑步
部署
與Nginx配合（推薦）
與阿帕契合作
啟用 WebSocket 伺服器
監聽事件
- 系統事件
- 自訂非同步事件
非同步任務佇列
毫秒 cron 作業
修改程式碼後自動重新載入
取得專案中SwooleServer的實例
使用SwooleTable
多埠混合協定
協程
客製化流程
通用元件
- 阿波羅
- 普羅米修斯
其他特點
- 配置 Swoole 事件
- 無伺服器
重要通知
使用者及案例
替代方案
贊助
執照

特徵

內建 Http/WebSocket 伺服器
多埠混合協定
客製化流程
記憶體駐留
非同步事件監聽
非同步任務佇列
毫秒 cron 作業
通用元件
優雅地重新加載
修改程式碼後自動重新載入
同時支援Laravel/Lumen，相容性好
簡單且開箱即用

基準

哪個是最快的 Web 框架？
TechEmpower 框架基準

要求

依賴性	要求
PHP	`>=8.2` `Recommend 8.2`
斯沃爾	`>=5.0` `Recommend 5.1.1`
Laravel/流明	`>=10` `Recommend 10`

安裝

1.需要透過Composer(packagist)進行打包。

 # PHP >=8.2
composer require " hhxsv5/laravel-s:~3.8.0 "

# PHP >=5.5.9,<=7.4.33
# composer require "hhxsv5/laravel-s:~3.7.0"

# Make sure that your composer.lock file is under the VCS

2.註冊服務提供者（二選一）。

Laravel : 在config/app.php檔案中， Laravel 5.5+ supports package discovery automatically, you should skip this step
```
 ' providers ' => [
    //...
    Hhxsv5  LaravelS  Illuminate LaravelSServiceProvider::class,
],
```

Lumen ：在bootstrap/app.php檔案中

 $ app -> register ( Hhxsv5  LaravelS  Illuminate LaravelSServiceProvider::class);

3.發布配置和二進位。

升級LaravelS後，需要重新發布；點擊這裡查看各個版本的變更說明。

php artisan laravels publish
# Configuration: config/laravels.php
# Binary: bin/laravels bin/fswatch bin/inotify

4.更改config/laravels.php ：listen_ip、listen_port，請參考設定。

5.性能調優

調整核心參數
Workers數量：LaravelS採用Swoole的Synchronous IO模式， worker_num設定越大，並發效能越好，但會造成更多的記憶體佔用和行程切換開銷。如果一個請求需要100ms，為了提供1000QPS的並發，至少需要配置100個Worker進程。計算方法為：worker_num = 1000QPS/(1s/1ms) = 100，因此需要增量壓測來計算最佳的worker_num 。
任務工人數量

跑步

Please read the notices carefully before running ，重要提示（IMPORTANT）。

指令： php bin/laravels {start|stop|restart|reload|info|help} 。

命令	描述
開始	啟動 LaravelS，透過「 ps -ef\|grep laravels 」列出進程
停止	停止LaravelS，並觸發自訂進程的`onStop`方法
重新啟動	重新啟動 LaravelS：啟動前優雅地停止；該服務在啟動完成之前`unavailable`
重新載入	重新載入所有包含您業務程式碼的Task/Worker/Timer進程，並觸發自訂進程的`onReload`方法，不能重新載入Master/Manger進程。修改`config/laravels.php`後， `only`呼叫`restart`即可重新啟動
資訊	顯示元件版本訊息
幫助	顯示幫助訊息

指令start和restart的引導選項。

選項	描述
-d\|--守護程式	作為守護程序運行，此選項將覆蓋`laravels.php`中的`swoole.daemonize`設置
-e\|--env	命令運行的環境，例如`--env=testing`將首先使用設定檔`.env.testing` ，此功能需要 Laravel 5.2+
-i\|--忽略	忽略檢查Master進程的PID文件
-x\|--x-版本	目前專案的版本（分支），儲存在$_ENV/$_SERVER中，透過`$_ENV['X_VERSION']` `$_SERVER['X_VERSION']` `$request->server->get('X_VERSION')`訪問

Runtime文件： start會自動執行php artisan laravels config並產生這些文件，開發者一般不需要關注，建議添加到.gitignore中。

文件	描述
儲存/laraves.conf	LaravelS 的`runtime`設定檔
儲存/laraves.pid	Master進程的PID文件
儲存/laravel-timer-process.pid	Timer進程的PID文件
儲存/laravels-custom-processes.pid	所有自訂進程的PID文件

部署

建議透過 Supervisord 來監控主進程，前提是不帶-d選項並且設定swoole.daemonize為false 。

 [program:laravel-s-test]
directory=/var/www/laravel-s-test
command=/usr/local/bin/php bin/laravels start -i
numprocs=1
autostart=true
autorestart=true
startretries=3
user=www-data
redirect_stderr=true
stdout_logfile=/var/log/supervisor/%(program_name)s.log

與Nginx配合（推薦）

演示。

 gzip on ;
gzip_min_length 1024 ;
gzip_comp_level 2 ;
gzip_types text/plain text/css text/javascript application/json application/javascript application/x-javascript application/xml application/x-httpd-php image/jpeg image/gif image/png font/ttf font/otf image/svg+xml;
gzip_vary on ;
gzip_disable "msie6" ;
upstream swoole {
    # Connect IP:Port
    server 127.0.0.1:5200 weight=5 max_fails=3 fail_timeout=30s;
    # Connect UnixSocket Stream file, tips: put the socket file in the /dev/shm directory to get better performance
    #server unix:/yourpath/laravel-s-test/storage/laravels.sock weight=5 max_fails=3 fail_timeout=30s;
    #server 192.168.1.1:5200 weight=3 max_fails=3 fail_timeout=30s;
    #server 192.168.1.2:5200 backup;
    keepalive 16;
}
server {
    listen 80 ;
    # Don't forget to bind the host
    server_name laravels.com;
    root /yourpath/laravel-s-test/public;
    access_log /yourpath/log/nginx/ $server_name .access.log  main ;
    autoindex off ;
    index index.html index.htm;
    # Nginx handles the static resources(recommend enabling gzip), LaravelS handles the dynamic resource.
    location / {
        try_files $uri @laravels;
    }
    # Response 404 directly when request the PHP file, to avoid exposing public/*.php
    #location ~* .php$ {
    #    return 404;
    #}
    location @laravels {
        # proxy_connect_timeout 60s;
        # proxy_send_timeout 60s;
        # proxy_read_timeout 120s;
        proxy_http_version 1.1 ;
        proxy_set_header Connection "" ;
        proxy_set_header X-Real-IP $remote_addr ;
        proxy_set_header X-Real-PORT $remote_port ;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for ;
        proxy_set_header Host $http_host ;
        proxy_set_header Scheme $scheme ;
        proxy_set_header Server-Protocol $server_protocol ;
        proxy_set_header Server-Name $server_name ;
        proxy_set_header Server-Addr $server_addr ;
        proxy_set_header Server-Port $server_port ;
        # "swoole" is the upstream
        proxy_pass http://swoole;
    }
}

與阿帕契合作

 LoadModule proxy_module /yourpath/modules/mod_proxy.so
LoadModule proxy_balancer_module /yourpath/modules/mod_proxy_balancer.so
LoadModule lbmethod_byrequests_module /yourpath/modules/mod_lbmethod_byrequests.so
LoadModule proxy_http_module /yourpath/modules/mod_proxy_http.so
LoadModule slotmem_shm_module /yourpath/modules/mod_slotmem_shm.so
LoadModule rewrite_module /yourpath/modules/mod_rewrite.so
LoadModule remoteip_module /yourpath/modules/mod_remoteip.so
LoadModule deflate_module /yourpath/modules/mod_deflate.so

< IfModule deflate_module>
    SetOutputFilter DEFLATE
    DeflateCompressionLevel 2
    AddOutputFilterByType DEFLATE text/html text/plain text/css text/javascript application/json application/javascript application/x-javascript application/xml application/x-httpd-php image/jpeg image/gif image/png font/ttf font/otf image/svg+xml
</ IfModule >

< VirtualHost *:80>
    # Don't forget to bind the host
    ServerName www.laravels.com
    ServerAdmin [email protected]

    DocumentRoot /yourpath/laravel-s-test/public;
    DirectoryIndex index.html index.htm
    < Directory "/">
        AllowOverride None
        Require all granted
    </ Directory >

    RemoteIPHeader X-Forwarded-For

    ProxyRequests Off
    ProxyPreserveHost On
    < Proxy balancer://laravels>  
        BalancerMember http://192.168.1.1:5200 loadfactor=7
        # BalancerMember http://192.168.1.2:5200 loadfactor=3
        # BalancerMember http://192.168.1.3:5200 loadfactor=1 status=+H
        ProxySet lbmethod=byrequests
    </ Proxy >
    # ProxyPass / balancer://laravels/
    # ProxyPassReverse / balancer://laravels/

    # Apache handles the static resources, LaravelS handles the dynamic resource.
    RewriteEngine On
    RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} !-d
    RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} !-f
    RewriteRule ^/(.*)$ balancer://laravels %{REQUEST_URI} [P,L]

    ErrorLog ${APACHE_LOG_DIR}/www.laravels.com.error.log
    CustomLog ${APACHE_LOG_DIR}/www.laravels.com.access.log combined
</ VirtualHost >

啟用 WebSocket 伺服器

WebSocket Sever 的監聽位址與 Http Server 相同。

1.建立WebSocket Handler類，並實作介面WebSocketHandlerInterface 。

 namespace App  Services ;
use Hhxsv5  LaravelS  Swoole  WebSocketHandlerInterface ;
use Swoole  Http  Request ;
use Swoole  Http  Response ;
use Swoole  WebSocket  Frame ;
use Swoole  WebSocket  Server ;
/**
 * @see https://www.swoole.co.uk/docs/modules/swoole-websocket-server
 */
class WebSocketService implements WebSocketHandlerInterface
{
    // Declare constructor without parameters
    public function __construct ()
    {
    }
    // public function onHandShake(Request $request, Response $response)
    // {
           // Custom handshake: https://www.swoole.co.uk/docs/modules/swoole-websocket-server-on-handshake
           // The onOpen event will be triggered automatically after a successful handshake
    // }
    public function onOpen ( Server $ server , Request $ request )
    {
        // Before the onOpen event is triggered, the HTTP request to establish the WebSocket has passed the Laravel route,
        // so Laravel's Request, Auth information are readable, Session is readable and writable, but only in the onOpen event.
        // Log::info('New WebSocket connection', [$request->fd, request()->all(), session()->getId(), session('xxx'), session(['yyy' => time()])]);
        // The exceptions thrown here will be caught by the upper layer and recorded in the Swoole log. Developers need to try/catch manually.
        $ server -> push ( $ request -> fd , ' Welcome to LaravelS ' );
    }
    public function onMessage ( Server $ server , Frame $ frame )
    {
        // Log::info('Received message', [$frame->fd, $frame->data, $frame->opcode, $frame->finish]);
        // The exceptions thrown here will be caught by the upper layer and recorded in the Swoole log. Developers need to try/catch manually.
        $ server -> push ( $ frame -> fd , date ( ' Y-m-d H:i:s ' ));
    }
    public function onClose ( Server $ server , $ fd , $ reactorId )
    {
        // The exceptions thrown here will be caught by the upper layer and recorded in the Swoole log. Developers need to try/catch manually.
    }
}

2.修改config/laravels.php 。

 // ...
' websocket '      => [
    ' enable '  => true , // Note: set enable to true
    ' handler ' =>  App  Services WebSocketService::class,
],
' swoole '         => [
    //...
    // Must set dispatch_mode in (2, 4, 5), see https://www.swoole.co.uk/docs/modules/swoole-server/configuration
    ' dispatch_mode ' => 2 ,
    //...
],
// ...

3.使用SwooleTable綁定FD&UserId，可選，Swoole Table Demo。也可以使用其他全域儲存服務，如Redis/Memcached/MySQL，但要注意多個Swoole Servers之間的FD可能會發生衝突。

4.與Nginx配合（推薦）

請參閱 WebSocket 代理

 map $http_upgrade $connection_upgrade {
    default upgrade;
    ''      close;
}
upstream swoole {
    # Connect IP:Port
    server 127.0.0.1:5200 weight=5 max_fails=3 fail_timeout=30s;
    # Connect UnixSocket Stream file, tips: put the socket file in the /dev/shm directory to get better performance
    #server unix:/yourpath/laravel-s-test/storage/laravels.sock weight=5 max_fails=3 fail_timeout=30s;
    #server 192.168.1.1:5200 weight=3 max_fails=3 fail_timeout=30s;
    #server 192.168.1.2:5200 backup;
    keepalive 16;
}
server {
    listen 80 ;
    # Don't forget to bind the host
    server_name laravels.com;
    root /yourpath/laravel-s-test/public;
    access_log /yourpath/log/nginx/ $server_name .access.log  main ;
    autoindex off ;
    index index.html index.htm;
    # Nginx handles the static resources(recommend enabling gzip), LaravelS handles the dynamic resource.
    location / {
        try_files $uri @laravels;
    }
    # Response 404 directly when request the PHP file, to avoid exposing public/*.php
    #location ~* .php$ {
    #    return 404;
    #}
    # Http and WebSocket are concomitant, Nginx identifies them by "location"
    # !!! The location of WebSocket is "/ws"
    # Javascript: var ws = new WebSocket("ws://laravels.com/ws");
    location =/ws {
        # proxy_connect_timeout 60s;
        # proxy_send_timeout 60s;
        # proxy_read_timeout: Nginx will close the connection if the proxied server does not send data to Nginx in 60 seconds; At the same time, this close behavior is also affected by heartbeat setting of Swoole.
        # proxy_read_timeout 60s;
        proxy_http_version 1.1 ;
        proxy_set_header X-Real-IP $remote_addr ;
        proxy_set_header X-Real-PORT $remote_port ;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for ;
        proxy_set_header Host $http_host ;
        proxy_set_header Scheme $scheme ;
        proxy_set_header Server-Protocol $server_protocol ;
        proxy_set_header Server-Name $server_name ;
        proxy_set_header Server-Addr $server_addr ;
        proxy_set_header Server-Port $server_port ;
        proxy_set_header Upgrade $http_upgrade ;
        proxy_set_header Connection $connection_upgrade ;
        proxy_pass http://swoole;
    }
    location @laravels {
        # proxy_connect_timeout 60s;
        # proxy_send_timeout 60s;
        # proxy_read_timeout 60s;
        proxy_http_version 1.1 ;
        proxy_set_header Connection "" ;
        proxy_set_header X-Real-IP $remote_addr ;
        proxy_set_header X-Real-PORT $remote_port ;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for ;
        proxy_set_header Host $http_host ;
        proxy_set_header Scheme $scheme ;
        proxy_set_header Server-Protocol $server_protocol ;
        proxy_set_header Server-Name $server_name ;
        proxy_set_header Server-Addr $server_addr ;
        proxy_set_header Server-Port $server_port ;
        proxy_pass http://swoole;
    }
}

5.心跳設定

Swoole的心跳設置

 // config/laravels.php
' swoole ' => [
    //...
    // All connections are traversed every 60 seconds. If a connection does not send any data to the server within 600 seconds, the connection will be forced to close.
    ' heartbeat_idle_time '      => 600 ,
    ' heartbeat_check_interval ' => 60 ,
    //...
],

Nginx的代理程式讀取逾時

 # Nginx will close the connection if the proxied server does not send data to Nginx in 60 seconds
proxy_read_timeout 60s ;

6.將資料推送到控制器中

 namespace App  Http  Controllers ;
class TestController extends Controller
{
    public function push ()
    {
        $ fd = 1 ; // Find fd by userId from a map [userId=>fd].
        /**@var SwooleWebSocketServer $swoole */
        $ swoole = app ( ' swoole ' );
        $ success = $ swoole -> push ( $ fd , ' Push data to fd#1 in Controller ' );
        var_dump ( $ success );
    }
}

監聽事件

系統事件

通常，您可以重置/銷毀一些global/static變量，或更改當前的Request/Response物件。

laravels.received_request在 LaravelS 解析SwooleHttpRequest為IlluminateHttpRequest之後，在 Laravel 的核心處理此請求之前。

 // Edit file `app/Providers/EventServiceProvider.php`, add the following code into method `boot`
// If no variable $events, you can also call Facade Event::listen(). 
$ events -> listen ( ' laravels.received_request ' , function (  Illuminate  Http  Request $ req , $ app ) {
    $ req -> query -> set ( ' get_key ' , ' hhxsv5 ' ); // Change query of request
    $ req -> request -> set ( ' post_key ' , ' hhxsv5 ' ); // Change post of request
});

laravels.generated_response在 Laravel 的核心處理請求之後，在 LaravelS 將IlluminateHttpResponse解析為SwooleHttpResponse之前。

 // Edit file `app/Providers/EventServiceProvider.php`, add the following code into method `boot`
// If no variable $events, you can also call Facade Event::listen(). 
$ events -> listen ( ' laravels.generated_response ' , function (  Illuminate  Http  Request $ req ,  Symfony  Component  HttpFoundation  Response $ rsp , $ app ) {
    $ rsp -> headers -> set ( ' header-key ' , ' hhxsv5 ' ); // Change header of response
});

自訂非同步事件

此功能依賴Swoole的AsyncTask ，需要先在config/laravels.php中設定swoole.task_worker_num 。非同步事件處理的效能受Swoole任務進程數量的影響，需要適當設定task_worker_num。

1.建立事件類別。

 use Hhxsv5  LaravelS  Swoole  Task  Event ;
class TestEvent extends Event
{
    protected $ listeners = [
        // Listener list
        TestListener1::class,
        // TestListener2::class,
    ];
    private $ data ;
    public function __construct ( $ data )
    {
        $ this -> data = $ data ;
    }
    public function getData ()
    {
        return $ this -> data ;
    }
}

2.建立監聽類別。

 use Hhxsv5  LaravelS  Swoole  Task  Event ;
use Hhxsv5  LaravelS  Swoole  Task  Task ;
use Hhxsv5  LaravelS  Swoole  Task  Listener ;
class TestListener1 extends Listener
{
    public function handle ( Event $ event )
    {
        Log:: info ( __CLASS__ . ' :handle start ' , [ $ event -> getData ()]);
        sleep ( 2 ); // Simulate the slow codes
        // Deliver task in CronJob, but NOT support callback finish() of task.
        // Note: Modify task_ipc_mode to 1 or 2 in config/laravels.php, see https://www.swoole.co.uk/docs/modules/swoole-server/configuration
        $ ret = Task:: deliver ( new TestTask ( ' task data ' ));
        var_dump ( $ ret );
        // The exceptions thrown here will be caught by the upper layer and recorded in the Swoole log. Developers need to try/catch manually.
        // return false; // Stop propagating this event to subsequent listeners
    }
}

3.火災事件。

 // Create instance of event and fire it, "fire" is asynchronous.
use Hhxsv5  LaravelS  Swoole  Task  Event ;
$ event = new TestEvent ( ' event data ' );
// $event->delay(10); // Delay 10 seconds to fire event
// $event->setTries(3); // When an error occurs, try 3 times in total
$ success = Event:: fire ( $ event );
var_dump ( $ success ); // Return true if sucess, otherwise false

非同步任務佇列

此功能依賴Swoole的AsyncTask ，需要先在config/laravels.php中設定swoole.task_worker_num 。任務處理的效能受Swoole任務進程數量的影響，需要適當設定task_worker_num。

1.創建任務類別。

 use Hhxsv5  LaravelS  Swoole  Task  Task ;
class TestTask extends Task
{
    private $ data ;
    private $ result ;
    public function __construct ( $ data )
    {
        $ this -> data = $ data ;
    }
    // The logic of task handling, run in task process, CAN NOT deliver task
    public function handle ()
    {
        Log:: info ( __CLASS__ . ' :handle start ' , [ $ this -> data ]);
        sleep ( 2 ); // Simulate the slow codes
        // The exceptions thrown here will be caught by the upper layer and recorded in the Swoole log. Developers need to try/catch manually.
        $ this -> result = ' the result of ' . $ this -> data ;
    }
    // Optional, finish event, the logic of after task handling, run in worker process, CAN deliver task 
    public function finish ()
    {
        Log:: info ( __CLASS__ . ' :finish start ' , [ $ this -> result ]);
        Task:: deliver ( new TestTask2 ( ' task2 data ' )); // Deliver the other task
    }
}

2.交付任務。

 // Create instance of TestTask and deliver it, "deliver" is asynchronous.
use Hhxsv5  LaravelS  Swoole  Task  Task ;
$ task = new TestTask ( ' task data ' );
// $task->delay(3);// delay 3 seconds to deliver task
// $task->setTries(3); // When an error occurs, try 3 times in total
$ ret = Task:: deliver ( $ task );
var_dump ( $ ret ); // Return true if sucess, otherwise false

毫秒 cron 作業

基於 Swoole 的毫秒計時器包裝 cron 作業，取代Linux Crontab 。

1.建立cron作業類別。

 namespace App  Jobs  Timer ;
use App  Tasks  TestTask ;
use Swoole  Coroutine ;
use Hhxsv5  LaravelS  Swoole  Task  Task ;
use Hhxsv5  LaravelS  Swoole  Timer  CronJob ;
class TestCronJob extends CronJob
{
    protected $ i = 0 ;
    // !!! The `interval` and `isImmediate` of cron job can be configured in two ways(pick one of two): one is to overload the corresponding method, and the other is to pass parameters when registering cron job.
    // --- Override the corresponding method to return the configuration: begin
    public function interval ()
    {
        return 1000 ; // Run every 1000ms
    }
    public function isImmediate ()
    {
        return false ; // Whether to trigger `run` immediately after setting up
    }
    // --- Override the corresponding method to return the configuration: end
    public function run ()
    {
        Log:: info ( __METHOD__ , [ ' start ' , $ this -> i , microtime ( true )]);
        // do something
        // sleep(1); // Swoole < 2.1
        Coroutine:: sleep ( 1 ); // Swoole>=2.1 Coroutine will be automatically created for run().
        $ this -> i ++;
        Log:: info ( __METHOD__ , [ ' end ' , $ this -> i , microtime ( true )]);

        if ( $ this -> i >= 10 ) { // Run 10 times only
            Log:: info ( __METHOD__ , [ ' stop ' , $ this -> i , microtime ( true )]);
            $ this -> stop (); // Stop this cron job, but it will run again after restart/reload.
            // Deliver task in CronJob, but NOT support callback finish() of task.
            // Note: Modify task_ipc_mode to 1 or 2 in config/laravels.php, see https://www.swoole.co.uk/docs/modules/swoole-server/configuration
            $ ret = Task:: deliver ( new TestTask ( ' task data ' ));
            var_dump ( $ ret );
        }
        // The exceptions thrown here will be caught by the upper layer and recorded in the Swoole log. Developers need to try/catch manually.
    }
}

2.註冊cron作業。

 // Register cron jobs in file "config/laravels.php"
[
    // ...
    ' timer '          => [
        ' enable ' => true , // Enable Timer
        ' jobs '   => [ // The list of cron job
            // Enable LaravelScheduleJob to run `php artisan schedule:run` every 1 minute, replace Linux Crontab
            // Hhxsv5LaravelSIlluminateLaravelScheduleJob::class,
            // Two ways to configure parameters:
            // [AppJobsTimerTestCronJob::class, [1000, true]], // Pass in parameters when registering
             App  Jobs  Timer TestCronJob::class, // Override the corresponding method to return the configuration
        ],
        ' max_wait_time ' => 5 , // Max waiting time of reloading
        // Enable the global lock to ensure that only one instance starts the timer when deploying multiple instances. This feature depends on Redis, please see https://laravel.com/docs/7.x/redis
        ' global_lock '     => false ,
        ' global_lock_key ' => config ( ' app.name ' , ' Laravel ' ),
    ],
    // ...
];

3.注意：建置伺服器叢集時會啟動多個計時器，因此您需要確保只啟動一個計時器，以避免執行重複的任務。

4.LaravelS v3.4.0開始支援熱重啟[Reload] Timer進程。 LaravelS 收到SIGUSR1訊號後，會等待max_wait_time （預設 5）秒結束進程，然後Manager進程會再次拉起Timer進程。

5.如果只需要使用minute-level定時任務，建議啟用Hhxsv5LaravelSIlluminateLaravelScheduleJob而不是 Linux Crontab，這樣可以遵循 Laravel 任務調度的編碼習慣並配置Kernel 。

 // app/Console/Kernel.php
protected function schedule ( Schedule $ schedule )
{
    // runInBackground() will start a new child process to execute the task. This is asynchronous and will not affect the execution timing of other tasks.
    $ schedule -> command (TestCommand::class)-> runInBackground ()-> everyMinute ();
}

修改程式碼後自動重新載入

透過inotify ，僅支援 Linux。
1.安裝inotify擴充。
2.打開設定中的開關。
3.注意：僅在Linux下修改檔案才能接收檔案變更事件。建議使用最新的Docker。流浪解決方案。
透過fswatch ，支援 OS X/Linux/Windows。
1.安裝fswatch。
2.在專案根目錄中執行指令。
```
 # Watch current directory
./bin/fswatch
# Watch app directory
./bin/fswatch ./app
```
透過inotifywait ，支援 Linux。
1.安裝inotify工具。
2.在專案根目錄中執行指令。
```
 # Watch current directory
./bin/inotify
# Watch app directory
./bin/inotify ./app
```
當以上方法都不起作用時，最終解決方案：設定max_request=1,worker_num=1 ，這樣Worker進程在處理完一個請求後會重新啟動。這種方法的效能很差， so only development environment use 。

取得專案中`SwooleServer`的實例

 /**
 * $swoole is the instance of `SwooleWebSocketServer` if enable WebSocket server, otherwise `SwooleHttpServer`
 * @var SwooleWebSocketServer|SwooleHttpServer $swoole
 */
$ swoole = app ( ' swoole ' );
var_dump ( $ swoole -> stats ());
$ swoole -> push ( $ fd , ' Push WebSocket message ' );

使用`SwooleTable`

1.定義Table，支援多個。

所有定義的表將在 Swoole 啟動之前建立。

 // in file "config/laravels.php"
[
    // ...
    ' swoole_tables '  => [
        // Scene：bind UserId & FD in WebSocket
        ' ws ' => [ // The Key is table name, will add suffix "Table" to avoid naming conflicts. Here defined a table named "wsTable"
            ' size '   => 102400 , // The max size
            ' column ' => [ // Define the columns
                [ ' name ' => ' value ' , ' type ' =>  Swoole Table:: TYPE_INT , ' size ' => 8 ],
            ],
        ],
        //...Define the other tables
    ],
    // ...
];

2.存取Table ：所有表格實例都會綁定在SwooleServer上，透過app('swoole')->xxxTable存取。

 namespace App  Services ;
use Hhxsv5  LaravelS  Swoole  WebSocketHandlerInterface ;
use Swoole  Http  Request ;
use Swoole  WebSocket  Frame ;
use Swoole  WebSocket  Server ;
class WebSocketService implements WebSocketHandlerInterface
{
    /**@var SwooleTable $wsTable */
    private $ wsTable ;
    public function __construct ()
    {
        $ this -> wsTable = app ( ' swoole ' )-> wsTable ;
    }
    // Scene：bind UserId & FD in WebSocket
    public function onOpen ( Server $ server , Request $ request )
    {
        // var_dump(app('swoole') === $server);// The same instance
        /**
         * Get the currently logged in user
         * This feature requires that the path to establish a WebSocket connection go through middleware such as Authenticate.
         * E.g:
         * Browser side: var ws = new WebSocket("ws://127.0.0.1:5200/ws");
         * Then the /ws route in Laravel needs to add the middleware like Authenticate.
         * Route::get('/ws', function () {
         *     // Respond any content with status code 200
         *     return 'websocket';
         * })->middleware(['auth']);
         */
        // $user = Auth::user();
        // $userId = $user ? $user->id : 0; // 0 means a guest user who is not logged in
        $ userId = mt_rand ( 1000 , 10000 );
        // if (!$userId) {
        //     // Disconnect the connections of unlogged users
        //     $server->disconnect($request->fd);
        //     return;
        // }
        $ this -> wsTable -> set ( ' uid: ' . $ userId , [ ' value ' => $ request -> fd ]); // Bind map uid to fd
        $ this -> wsTable -> set ( ' fd: ' . $ request -> fd , [ ' value ' => $ userId ]); // Bind map fd to uid
        $ server -> push ( $ request -> fd , " Welcome to LaravelS # { $ request -> fd }" );
    }
    public function onMessage ( Server $ server , Frame $ frame )
    {
        // Broadcast
        foreach ( $ this -> wsTable as $ key => $ row ) {
            if ( strpos ( $ key , ' uid: ' ) === 0 && $ server -> isEstablished ( $ row [ ' value ' ])) {
                $ content = sprintf ( ' Broadcast: new message "%s" from #%d ' , $ frame -> data , $ frame -> fd );
                $ server -> push ( $ row [ ' value ' ], $ content );
            }
        }
    }
    public function onClose ( Server $ server , $ fd , $ reactorId )
    {
        $ uid = $ this -> wsTable -> get ( ' fd: ' . $ fd );
        if ( $ uid !== false ) {
            $ this -> wsTable -> del ( ' uid: ' . $ uid [ ' value ' ]); // Unbind uid map
        }
        $ this -> wsTable -> del ( ' fd: ' . $ fd ); // Unbind fd map
        $ server -> push ( $ fd , " Goodbye # { $ fd }" );
    }
}

多埠混合協定

更多資訊請參考 Swoole Server AddListener

為了讓我們的主伺服器支援更多的協議，而不僅僅是 Http 和 WebSocket，我們在 LaravelS 中引入了 Swoole 的multi-port mixed protocol功能，並將其命名為Socket 。現在，您可以在 Laravel 之上輕鬆建立TCP/UDP應用程式。

建立Socket處理程序類，並擴充Hhxsv5LaravelSSwooleSocket{TcpSocket|UdpSocket|Http|WebSocket} 。

 namespace App  Sockets ;
use Hhxsv5  LaravelS  Swoole  Socket  TcpSocket ;
use Swoole  Server ;
class TestTcpSocket extends TcpSocket
{
    public function onConnect ( Server $ server , $ fd , $ reactorId )
    {
        Log:: info ( ' New TCP connection ' , [ $ fd ]);
        $ server -> send ( $ fd , ' Welcome to LaravelS. ' );
    }
    public function onReceive ( Server $ server , $ fd , $ reactorId , $ data )
    {
        Log:: info ( ' Received data ' , [ $ fd , $ data ]);
        $ server -> send ( $ fd , ' LaravelS: ' . $ data );
        if ( $ data === " quit rn" ) {
            $ server -> send ( $ fd , ' LaravelS: bye ' . PHP_EOL );
            $ server -> close ( $ fd );
        }
    }
    public function onClose ( Server $ server , $ fd , $ reactorId )
    {
        Log:: info ( ' Close TCP connection ' , [ $ fd ]);
        $ server -> send ( $ fd , ' Goodbye ' );
    }
}

這些Socket連線與HTTP / WebSocket連線共享相同的工作進程。所以如果你要交付任務，使用SwooleTable ，甚至是 DB、Eloquent 等 Laravel 元件，完全不成問題。同時，您可以透過成員屬性swoolePort直接存取SwooleServerPort物件。

 public function onReceive ( Server $ server , $ fd , $ reactorId , $ data )
{
    $ port = $ this -> swoolePort ; // Get the `SwooleServerPort` object
}

 namespace App  Http  Controllers ;
class TestController extends Controller
{
    public function test ()
    {
        /**@var SwooleHttpServer|SwooleWebSocketServer $swoole */
        $ swoole = app ( ' swoole ' );
        // $swoole->ports: Traverse all Port objects, https://www.swoole.co.uk/docs/modules/swoole-server/multiple-ports
        $ port = $ swoole -> ports [ 0 ]; // Get the `SwooleServerPort` object, $port[0] is the port of the main server
        foreach ( $ port -> connections as $ fd ) { // Traverse all connections
            // $swoole->send($fd, 'Send tcp message');
            // if($swoole->isEstablished($fd)) {
            //     $swoole->push($fd, 'Send websocket message');
            // }
        }
    }
}

註冊套接字。

 // Edit `config/laravels.php`
//...
' sockets ' => [
    [
        ' host '     => ' 127.0.0.1 ' ,
        ' port '     => 5291 ,
        ' type '     => SWOOLE_SOCK_TCP , // Socket type: SWOOLE_SOCK_TCP/SWOOLE_SOCK_TCP6/SWOOLE_SOCK_UDP/SWOOLE_SOCK_UDP6/SWOOLE_UNIX_DGRAM/SWOOLE_UNIX_STREAM
        ' settings ' => [ // Swoole settings：https://www.swoole.co.uk/docs/modules/swoole-server-methods#swoole_server-addlistener
            ' open_eof_check ' => true ,
            ' package_eof '    => "rn" ,
        ],
        ' handler '  =>  App  Sockets TestTcpSocket::class,
        ' enable '   => true , // whether to enable, default true
    ],
],

關於心跳配置，只能在main server上設置，不能在Socket上配置，但Socket繼承了main server的心跳配置。

對於TCP套接字，當Swoole的dispatch_mode為1/3時， onConnect和onClose事件將會被阻塞，所以如果你想解除對這兩個事件的阻塞，請將dispatch_mode設為2/4/5 。

 ' swoole ' => [
    //...
    ' dispatch_mode ' => 2 ,
    //...
];

測試。

TCP： telnet 127.0.0.1 5291
UDP: [Linux] echo "Hello LaravelS" > /dev/udp/127.0.0.1/5292

註冊其他協定的範例。

UDP協定

 ' sockets ' => [
    [
        ' host '     => ' 0.0.0.0 ' ,
        ' port '     => 5292 ,
        ' type '     => SWOOLE_SOCK_UDP ,
        ' settings ' => [
            ' open_eof_check ' => true ,
            ' package_eof '    => "rn" ,
        ],
        ' handler '  =>  App  Sockets TestUdpSocket::class,
    ],
],

HTTP

 ' sockets ' => [
    [
        ' host '     => ' 0.0.0.0 ' ,
        ' port '     => 5293 ,
        ' type '     => SWOOLE_SOCK_TCP ,
        ' settings ' => [
            ' open_http_protocol ' => true ,
        ],
        ' handler '  =>  App  Sockets TestHttp::class,
    ],
],

WebSocket：主伺服器必須turn on WebSocket ，即將websocket.enable設定為true 。

 ' sockets ' => [
    [
        ' host '     => ' 0.0.0.0 ' ,
        ' port '     => 5294 ,
        ' type '     => SWOOLE_SOCK_TCP ,
        ' settings ' => [
            ' open_http_protocol '      => true ,
            ' open_websocket_protocol ' => true ,
        ],
        ' handler '  =>  App  Sockets TestWebSocket::class,
    ],
],

協程

Swoole協程

警告：協程中程式碼執行的順序是亂序的。請求層級的資料應該透過協程ID隔離。然而，Laravel/Lumen 中存在著許多單例和靜態屬性，不同請求之間的資料會互相影響，這是Unsafe 。例如，資料庫連線是單例的，同一個資料庫連線共享同一個PDO資源。這在同步阻塞模式下沒問題，但在非同步協程模式下就不行了。每個查詢需要建立不同的連線並維護不同連線的IO狀態，這就需要連線池。
DO NOT啟用協程，只有自訂進程可以使用協程。

客製化流程

支援開發人員建立用於監控、報告或其他特殊任務的特殊工作流程。參考addProcess.

建立Process類，實作CustomProcessInterface。

 namespace App  Processes ;
use App  Tasks  TestTask ;
use Hhxsv5  LaravelS  Swoole  Process  CustomProcessInterface ;
use Hhxsv5  LaravelS  Swoole  Task  Task ;
use Swoole  Coroutine ;
use Swoole  Http  Server ;
use Swoole  Process ;
class TestProcess implements CustomProcessInterface
{
    /**
     * @var bool Quit tag for Reload updates
     */
    private static $ quit = false ;

    public static function callback ( Server $ swoole , Process $ process )
    {
        // The callback method cannot exit. Once exited, Manager process will automatically create the process 
        while (! self :: $ quit ) {
            Log:: info ( ' Test process: running ' );
            // sleep(1); // Swoole < 2.1
            Coroutine:: sleep ( 1 ); // Swoole>=2.1: Coroutine & Runtime will be automatically enabled for callback(). Pay attention to the compatibility between the components used and the coroutines. If they are not compatible, only some coroutines can be enabled, such as: SwooleRuntime::enableCoroutine(SWOOLE_HOOK_TCP | SWOOLE_HOOK_SLEEP | SWOOLE_HOOK_FILE);
             // Deliver task in custom process, but NOT support callback finish() of task.
            // Note: Modify task_ipc_mode to 1 or 2 in config/laravels.php, see https://www.swoole.co.uk/docs/modules/swoole-server/configuration
            $ ret = Task:: deliver ( new TestTask ( ' task data ' ));
            var_dump ( $ ret );
            // The upper layer will catch the exception thrown in the callback and record it in the Swoole log, and then this process will exit. The Manager process will re-create the process after 3 seconds, so developers need to try/catch to catch the exception by themselves to avoid frequent process creation.
            // throw new Exception('an exception');
        }
    }
    // Requirements: LaravelS >= v3.4.0 & callback() must be async non-blocking program.
    public static function onReload ( Server $ swoole , Process $ process )
    {
        // Stop the process...
        // Then end process
        Log:: info ( ' Test process: reloading ' );
        self :: $ quit = true ;
        // $process->exit(0); // Force exit process
    }
    // Requirements: LaravelS >= v3.7.4 & callback() must be async non-blocking program.
    public static function onStop ( Server $ swoole , Process $ process )
    {
        // Stop the process...
        // Then end process
        Log:: info ( ' Test process: stopping ' );
        self :: $ quit = true ;
        // $process->exit(0); // Force exit process
    }
}

註冊測試流程。

 // Edit `config/laravels.php`
// ...
' processes ' => [
    ' test ' => [ // Key name is process name
        ' class '    =>  App  Processes TestProcess::class,
        ' redirect ' => false , // Whether redirect stdin/stdout, true or false
        ' pipe '     => 0 ,     // The type of pipeline, 0: no pipeline 1: SOCK_STREAM 2: SOCK_DGRAM
        ' enable '   => true ,  // Whether to enable, default true
        //'num'    => 3   // To create multiple processes of this class, default is 1
        //'queue'    => [ // Enable message queue as inter-process communication, configure empty array means use default parameters
        //    'msg_key'  => 0,    // The key of the message queue. Default: ftok(__FILE__, 1).
        //    'mode'     => 2,    // Communication mode, default is 2, which means contention mode
        //    'capacity' => 8192, // The length of a single message, is limited by the operating system kernel parameters. The default is 8192, and the maximum is 65536
        //],
        //'restart_interval' => 5, // After the process exits abnormally, how many seconds to wait before restarting the process, default 5 seconds
    ],
],

注意：callback() 不能退出。如果退出，Manager進程將重新建立進程。

範例：將資料寫入自訂進程。

 // config/laravels.php
' processes ' => [
    ' test ' => [
        ' class '    =>  App  Processes TestProcess::class,
        ' redirect ' => false ,
        ' pipe '     => 1 ,
    ],
],

 // app/Processes/TestProcess.php
public static function callback ( Server $ swoole , Process $ process )
{
    while ( $ data = $ process -> read ()) {
        Log:: info ( ' TestProcess: read data ' , [ $ data ]);
        $ process -> write ( ' TestProcess: ' . $ data );
    }
}

 // app/Http/Controllers/TestController.php
public function testProcessWrite ()
{
    /**@var SwooleProcess[] $process */
    $ customProcesses =  Hhxsv5  LaravelS LaravelS:: getCustomProcesses ();
    $ process = $ customProcesses [ ' test ' ];
    $ process -> write ( ' TestController: write data ' . time ());
    var_dump ( $ process -> read ());
}

通用元件

阿波羅

LaravelS啟動時會拉取Apollo設定並將其寫入.env檔。同時， LaravelS會啟動自訂進程apollo來監控配置，並在配置變更時自動reload 。

啟用 Apollo：啟動參數中新增--enable-apollo和 Apollo 參數。

php bin/laravels start --enable-apollo --apollo-server=http://127.0.0.1:8080 --apollo-app-id=LARAVEL-S-TEST

支援熱更新（可選）。

 // Edit `config/laravels.php`
' processes ' => Hhxsv5  LaravelS  Components  Apollo Process:: getDefinition (),

 // When there are other custom process configurations
' processes ' => [
    ' test ' => [
        ' class '    =>  App  Processes TestProcess::class,
        ' redirect ' => false ,
        ' pipe '     => 1 ,
    ],
    // ...
] + Hhxsv5  LaravelS  Components  Apollo Process:: getDefinition (),

可用參數列表。

範圍	描述	預設	示範
阿波羅伺服器	Apollo 伺服器 URL	-	--apollo-server=http://127.0.0.1:8080
阿波羅應用程式 ID	阿波羅APP ID	-	--apollo-app-id=LARAVEL-S-TEST
阿波羅命名空間	APP所屬命名空間，支援指定多個	應用	--apollo-namespaces=應用程式 --apollo-namespaces=env
阿波羅星團	APP所屬集群	預設	--apollo-cluster=預設
apollo 用戶端 IP	目前實例的IP，也可用於灰階發布	本地內網IP	--apollo-client-ip=10.2.1.83
阿波羅拉超時	拉取配置超時時間（秒）	5	--apollo-pull-timeout=5
阿波羅備份舊環境	更新設定檔`.env`時是否備份舊設定文件	錯誤的	--apollo-backup-old-env

普羅米修斯

支援Prometheus監控警報，Grafana可視化查看監控指標。 Prometheus和Grafana的環境搭建請參考Docker Compose。

需要擴充 APCu >= 5.0.0，請透過pecl install apcu安裝。
將設定檔prometheus.php複製到專案的config目錄中。根據需要修改配置。
```
 # Execute commands in the project root directory
cp vendor/hhxsv5/laravel-s/config/prometheus.php config/
```
如果你的專案是Lumen ，還需要手動載入設定$app->configure('prometheus');在bootstrap/app.php中。
配置global中間件： Hhxsv5LaravelSComponentsPrometheusRequestMiddleware::class 。為了盡可能準確地統計請求時間消耗， RequestMiddleware必須是first全域中間件，需要放置在其他中介軟體的前面。
註冊 ServiceProvider： Hhxsv5LaravelSComponentsPrometheusServiceProvider::class 。

在config/laravels.php中設定 CollectorProcess，定期收集 Swoole Worker/Task/Timer 進程的指標。

 ' processes ' => Hhxsv5  LaravelS  Components  Prometheus CollectorProcess:: getDefinition (),

建立輸出指標的路由。

 use Hhxsv5  LaravelS  Components  Prometheus  Exporter ;

Route:: get ( ' /actuator/prometheus ' , function () {
    $ result = app (Exporter::class)-> render ();
    return response ( $ result , 200 , [ ' Content-Type ' => Exporter:: REDNER_MIME_TYPE ]);
});

完成Prometheus的配置並啟動。

 global :
  scrape_interval : 5s
  scrape_timeout : 5s
  evaluation_interval : 30s
scrape_configs :
- job_name : laravel-s-test
  honor_timestamps : true
  metrics_path : /actuator/prometheus
  scheme : http
  follow_redirects : true
  static_configs :
  - targets :
    - 127.0.0.1:5200 # The ip and port of the monitored service
# Dynamically discovered using one of the supported service-discovery mechanisms
# https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config
# - job_name: laravels-eureka
#   honor_timestamps: true
#   scrape_interval: 5s
#   metrics_path: /actuator/prometheus
#   scheme: http
#   follow_redirects: true
  # eureka_sd_configs:
  # - server: http://127.0.0.1:8080/eureka
  #   follow_redirects: true
  #   refresh_interval: 5s

啟動 Grafana，然後導入面板 json。

其他特點

配置 Swoole 事件

支持的活動：

事件	介面	什麼時候發生的
伺服器啟動	Hhxsv5LaravelSSwooleEventsServerStartInterface	Master進程啟動時發生， `this event should not handle complex business logic, and can only do some simple work of initialization` 。
伺服器停止	Hhxsv5LaravelSSwooleEventsServerStopInterface	當伺服器正常退出時發生， `CANNOT use async or coroutine related APIs in this event` 。
工人啟動	Hhxsv5LaravelSSwooleEventsWorkerStartInterface	Worker/Task進程啟動後，Laravel初始化完成後發生。
工人停止	Hhxsv5LaravelSSwooleEventsWorkerStopInterface	Worker/Task進程正常退出後發生
工人錯誤	Hhxsv5LaravelSSwooleEventsWorkerErrorInterface	當Worker/Task進程發生異常或致命錯誤時發生

1.建立事件類，實現對應的介面。

 namespace App  Events ;
use Hhxsv5  LaravelS  Swoole  Events  ServerStartInterface ;
use Swoole  Atomic ;
use Swoole  Http  Server ;
class ServerStartEvent implements ServerStartInterface
{
    public function __construct ()
    {
    }
    public function handle ( Server $ server )
    {
        // Initialize a global counter (available across processes)
        $ server -> atomicCount = new Atomic ( 2233 );

        // Invoked in controller: app('swoole')->atomicCount->get();
    }
}

 namespace App  Events ;
use Hhxsv5  LaravelS  Swoole  Events  WorkerStartInterface ;
use Swoole  Http  Server ;
class WorkerStartEvent implements WorkerStartInterface
{
    public function __construct ()
    {
    }
    public function handle ( Server $ server , $ workerId )
    {
        // Initialize a database connection pool
        // DatabaseConnectionPool::init();
    }
}

2.配置。

 // Edit `config/laravels.php`
' event_handlers ' => [
    ' ServerStart ' => [ App  Events ServerStartEvent::class], // Trigger events in array order
    ' WorkerStart ' => [ App  Events WorkerStartEvent::class],
],

無伺服器

阿里雲函數運算

函數計算。

1.修改bootstrap/app.php並設定儲存目錄。由於專案目錄是唯讀的，因此/tmp目錄只能讀寫。

 $ app -> useStoragePath ( env ( ' APP_STORAGE_PATH ' , ' /tmp/storage ' ));

2.建立shell腳本laravels_bootstrap並授予executable permission 。

 #! /usr/bin/env bash
set +e

# Create storage-related directories
mkdir -p /tmp/storage/app/public
mkdir -p /tmp/storage/framework/cache
mkdir -p /tmp/storage/framework/sessions
mkdir -p /tmp/storage/framework/testing
mkdir -p /tmp/storage/framework/views
mkdir -p /tmp/storage/logs

# Set the environment variable APP_STORAGE_PATH, please make sure it's the same as APP_STORAGE_PATH in .env
export APP_STORAGE_PATH=/tmp/storage

# Start LaravelS
php bin/laravels start

3.配置template.xml 。

ROSTemplateFormatVersion: '2015-09-01'
Transform: 'Aliyun::Serverless-2018-04-03'
Resources:
  laravel-s-demo:
    Type: 'Aliyun::Serverless::Service'
    Properties:
      Description: 'LaravelS Demo for Serverless'
    fc-laravel-s:
      Type: 'Aliyun::Serverless::Function'
      Properties:
        Handler: laravels.handler
        Runtime: custom
        MemorySize: 512
        Timeout: 30
        CodeUri: ./
        InstanceConcurrency: 10
        EnvironmentVariables:
          BOOTSTRAP_FILE: laravels_bootstrap

重要通知

單例問題

FPM模式下，每次請求都會實例化並回收單例實例，請求開始=>實例化實例=>請求結束=>回收實例。
在Swoole Server下，所有單例實例都會保存在記憶體中，與FPM的生命週期不同，請求開始=>實例化實例=>請求結束=>不回收單例實例。因此需要開發人員在每個請求中維護單例實例的狀態。
常見解決方案：
1. 編寫一個XxxCleaner類別來清理單例物件狀態。此類實作介面Hhxsv5LaravelSIlluminateCleanersCleanerInterface ，然後將其註冊到laravels.php的cleaners 。
2. 透過Middleware Reset單例實例的狀態。
3. 重新註冊ServiceProvider ，將XxxServiceProvider加入到laravels.php檔案的register_providers中。這樣在每個請求Refer中都會重新初始化單例實例。

清潔工

配置清理器。

已知問題

已知問題：已知問題和解決方案包。

偵錯方法

記錄；如果想要輸出到控制台，可以使用stderr ， Log::channel('stderr')->debug('debug message')。
Laravel Dump Server（Laravel 5.7 已預設為整合）。

讀取請求

透過IlluminateHttpRequest物件讀取要求，$_ENV 可讀，$_SERVER 部分可讀， CANNOT USE $_GET/$_POST/$_FILES/$_COOKIE/$_REQUEST/$_SESSION/$GLOBALS。

 public function form (  Illuminate  Http  Request $ request )
{
    $ name = $ request -> input ( ' name ' );
    $ all = $ request -> all ();
    $ sessionId = $ request -> cookie ( ' sessionId ' );
    $ photo = $ request -> file ( ' photo ' );
    // Call getContent() to get the raw POST body, instead of file_get_contents('php://input')
    $ rawContent = $ request -> getContent ();
    //...
}

輸出響應

透過IlluminateHttpResponse物件回應，相容於 echo/vardump()/print_r()， CANNOT USE函數 dd()/exit()/die()/header()/setcookie()/http_response_code()。

 public function json ()
{
    return response ()-> json ([ ' time ' => time ()])-> header ( ' header1 ' , ' value1 ' )-> withCookie ( ' c1 ' , ' v1 ' );
}

持久連接

Singleton connection會常駐內存，建議開啟persistent connection以獲得更好的效能。

資料庫連接，斷開後will immediately自動重新連接。

 // config/database.php
' connections ' => [
    ' my_conn ' => [
        ' driver '    => ' mysql ' ,
        ' host '      => env ( ' DB_MY_CONN_HOST ' , ' localhost ' ),
        ' port '      => env ( ' DB_MY_CONN_PORT ' , 3306 ),
        ' database '  => env ( ' DB_MY_CONN_DATABASE ' , ' forge ' ),
        ' username '  => env ( ' DB_MY_CONN_USERNAME ' , ' forge ' ),
        ' password '  => env ( ' DB_MY_CONN_PASSWORD ' , '' ),
        ' charset '   => ' utf8mb4 ' ,
        ' collation ' => ' utf8mb4_unicode_ci ' ,
        ' prefix '    => '' ,
        ' strict '    => false ,
        ' options '   => [
            // Enable persistent connection
             PDO :: ATTR_PERSISTENT => true ,
        ],
    ],
],

Redis連接，斷開後won't immediately自動重新連接，並且會拋出連接丟失的異常，下次重新連接。每次操作Redis之前都需要確保SELECT DB正確。

 // config/database.php
' redis ' => [
    ' client ' => env ( ' REDIS_CLIENT ' , ' phpredis ' ), // It is recommended to use phpredis for better performance.
    ' default ' => [
        ' host '       => env ( ' REDIS_HOST ' , ' localhost ' ),
        ' password '   => env ( ' REDIS_PASSWORD ' , null ),
        ' port '       => env ( ' REDIS_PORT ' , 6379 ),
        ' database '   => 0 ,
        ' persistent ' => true , // Enable persistent connection
    ],
],

關於記憶體洩漏

避免使用全域變數。如有必要，請手動清潔或重設它們。

無限追加元素到static / global變數中將導致 OOM（記憶體不足）。

 class Test
{
    public static $ array = [];
    public static $ string = '' ;
}

// Controller
public function test ( Request $ req )
{
    // Out of Memory
    Test:: $ array [] = $ req -> input ( ' param1 ' );
    Test:: $ string .= $ req -> input ( ' param2 ' );
}

記憶體洩漏檢測方法
1. 修改config/laravels.php : worker_num=1, max_request=1000000 ，測試後記得改回來；
2. 新增無route middleware路由/debug-memory-leak用於觀察Worker進程的記憶體變化；
```
Route:: get ( ' /debug-memory-leak ' , function () {
    global $ previous ;
    $ current = memory_get_usage ();
    $ stats = [
        ' prev_mem ' => $ previous ,
        ' curr_mem ' => $ current ,
        ' diff_mem ' => $ current - $ previous ,
    ];
    $ previous = $ current ;
    return $ stats ;
});
```
1. 啟動LaravelS並請求/debug-memory-leak直到diff_mem小於或等於 0；如果diff_mem始終大於零，則表示Global Middleware或Laravel Framework可能有記憶體洩漏；
2. 完成Step 3後， alternately請求業務路由和/debug-memory-leak （建議使用ab / wrk大量請求業務路由），初期記憶體增加正常。業務路由大量請求後，如果diff_mem始終大於0，且curr_mem持續增大，則很有可能出現記憶體洩漏；如果curr_mem總是在一定範圍內變化，並且不繼續增加，則記憶體洩漏的機率較低。
3. 如果還是解決不了，max_request是最後的保證。

Linux核心參數調整

Linux核心參數調整

壓力測試

壓力測試

替代方案

swooletw/laravel-swoole

贊助

貝寶
比特幣
吉泰

執照

麻省理工學院

展開

laravel s

持續更新

目錄

特徵

基準

要求

安裝

跑步

部署

與Nginx配合（推薦）

與阿帕契合作

啟用 WebSocket 伺服器

監聽事件

系統事件

自訂非同步事件

非同步任務佇列

毫秒 cron 作業

修改程式碼後自動重新載入

取得專案中SwooleServer的實例

使用SwooleTable

多埠混合協定

協程

客製化流程

通用元件

阿波羅

普羅米修斯

其他特點

配置 Swoole 事件

無伺服器

阿里雲函數運算

重要通知

單例問題

清潔工

已知問題

偵錯方法

讀取請求

輸出響應

持久連接

關於記憶體洩漏

Linux核心參數調整

壓力測試

替代方案

贊助

執照

取得專案中`SwooleServer`的實例

使用`SwooleTable`