Please answer these questions before submitting your issue. Thanks!

1. What did you do? If possible, provide a recipe for reproducing the error.

read Chinese and English documentation

2. What did you expect to see?

I expected to find best practice for production usage

3. What did you see instead?

nothing

4. What version of Swoole are you using (php --ri swoole)?

latest.

像Laravel 的集合类的高阶消息，用起来就很 Nice，例如：

$collect->map(function($item){
       return $item['value'];
});
// 可以写成这样
$collect->map->value;

// 方法调用
$collect->map(function($item){
       return $item->foo();
});
// 可以写成这样
$collect->map->foo();

// ...

Is your feature request related to a problem? Please describe.
I got few migrations each referring a different connection. migrate:fresh, migrate:refresh doesn't handle this scenario since they operate on the default connection or in the specific connection passed via --database param.

Describe the solution you'd like
The simplest solution can be to process only migrations that has th

SMProxy的账号密码端口和ip能设置与原mysql一样的吗?比如都设置为 127.0.0.1 root 123456 3306
目的是为了防止这个访问突然断了后直接连回mysql,或者说这服务有守护进程在的吗?服务挂了会重启或服务器挂了重启它也跟着重启而不需要手动启动

Hey,

I did a lot of work for authorization for your project. The first one is to use your project with concrete5 and the second one is to authorize the requests with jwt including the websocket server. This would maybe be a good example package for your documentation, how somebody could include authorization? I know it's not an issue, but i dont know how to reach you :)
https://github.com/lemo

PSR的RequestInterface没有规定实现exec方法，所以我设计组装一个http客户端无关的request的时候，我肯定不能绑定和客户端强相关的exec方法到Request上，因为每个客户端的异常类型、处理逻辑都不相同。

我设计一个composer组件，在组装请求部分，返回了个psr对象，本意是guzzle或者saber等支持PSR标准的HTTP客户端都可以按psr标准把这个对象代表的请求发送出去，现在Guzzle可以做到（$guzzleClient->send($PSRrequest)）而saber因为把PSR相关的处理逻辑绑定到他自定义的Request上，导致这样的设计没法实施。