Can not get public assets?

[mouyong]

When I run it in laravel project and use dcat-admin + tenancy it say those error. but in php-fpm, it can run success.

[mouyong]

Cann't.

When I use (new Response)->withFile(); it throw error: Error: Class "Workerman\Protocols\Http\Response" not found in xxx

Because the workerman version is so old in composer.lock.

server.php:

<?php

require_once __DIR__ . '/vendor/autoload.php';

use Adapterman\Adapterman;
use Workerman\Worker;

Adapterman::init();

$http_worker                = new Worker('http://0.0.0.0:3000');
$http_worker->count         = 8;
$http_worker->name          = 'AdapterMan';

$http_worker->onWorkerStart = static function () {
    //init();
    require __DIR__.'/public/start.php';
};

$http_worker->onMessage = static function ($connection, $request) {
    $file = __DIR__."/public/".ltrim($_SERVER['REQUEST_URI'] ?? '', '/');

    if (str_contains($file, '..')) {
        $response = new \Workerman\Protocols\Http\Response(403);

        return $connection->send($response);
    }

    if (is_file($file)) {
        $response = new \Workerman\Protocols\Http\Response();
        $response->withFile($file);

        return $connection->send($response);
    }

    $connection->send(run());
};

Worker::runAll();

Document: https://www.workerman.net/doc/workerman/http/response.html

[mouyong]

composer config repositories.adapterman vcs https://github.com/mouyong/AdapterMan

composer require joanhey/adapterman:dev-master

server.php

<?php

require_once __DIR__ . '/vendor/autoload.php';

use Adapterman\Adapterman;
use Workerman\Worker;

Adapterman::init();

$http_worker                = new Worker('http://0.0.0.0:3000');
$http_worker->count         = 8;
$http_worker->name          = 'AdapterMan';

$http_worker->onWorkerStart = static function () {
    //init();
    require __DIR__.'/public/start.php';
};

$http_worker->onMessage = static function ($connection, $request) {
    $file = __DIR__."/public/".ltrim($_SERVER['REQUEST_URI'] ?? '', '/');

    if (str_contains($file, '..')) {
        $response = new \Workerman\Protocols\Http\Response(403);

        return $connection->send($response);
    }

    if (is_file($file)) {
        $response = new \Workerman\Protocols\Http\Response();
        $response->withFile($file);

        return $connection->send($response);
    }

    $connection->send(run());
};

Worker::runAll();

[joanhey]

For now Adapterman only use Workerman 3.5.

Initally, Adapterman will be an App Server, and use a web server for the static files (Nginx, Nginx Unit, Apache, ...)

We can add to server static files too, but I think that is better handled by web servers : serve statics assets, TLS termination, Proxy, ...

But we are open to any ideas.

[joanhey]

In theory, if anybody want to use Adapterman with a popular framework, it's only for the performance.

The only way to scale more, it's use Adapterman , without any webserver, in separate servers. And you use a load balanced proxy server, to scale still more.
Or add different Workerman Apps (in the same server or not) to the same domain.
We need to abandon the monolithic apps.

Adapterman help to run any framework. But if you want to use all the features of Workerman, you can create more apps outside of your framework app.

[joanhey]

Example with Nginx:

location / {
         proxy_pass 127.0.0.1:8080;
         proxy_http_version 1.1;
         proxy_set_header Connection "";
}

[mouyong]

[mouyong]

it already proxy_pass to application, but cann't load laravel public path files.

[mouyong]

[joanhey]

We only change the php-fpm for a proxy_pass, the rest of the config is the same than normal Laravel.

Example normal Laravel config:

server {
    listen 80 default_server;
    listen [::]:80 default_server ipv6only=on;

    root /var/www/html/blog/public;
    index index.php index.html index.htm index.nginx-debian.html;

    server_name localhost;

    location / {
    try_files $uri $uri/ /index.php$is_args$args;
    }

    location ~ \.php$ {
      try_files $uri /index.php =404;
      fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
      fastcgi_index index.php;
      fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;
      include fastcgi_params;
    }

    location ~ /\.ht {
        deny all;
    }
}

With Adapterman:

server {
    listen 80 default_server;
    listen [::]:80 default_server ipv6only=on;

    root /var/www/html/blog/public;
    index index.php index.html index.htm index.nginx-debian.html;

    server_name localhost;

    location / {
    try_files $uri $uri/ @backend;
    }

    location @backend {
         proxy_pass 127.0.0.1:8080; // or localhost:8080;
         proxy_http_version 1.1;
         proxy_set_header Connection "";
    }

    location ~ /\.ht {
        deny all;
    }
}

[joanhey]

The config is the same than Nodejs or others app servers.

[mouyong]

it success load login page, but it cannot login by session.

[mouyong]

the problem key is those in picture.

[joanhey]

We need to test more the session.
But I tested with Symfony and various Laravel apps without problems.

[mouyong]

can you give me your mail address? i can give you site address and account/password.

[mouyong]

maybe i should try create a new laravel project and install dcat/laravel-admin, then test adapterman in tomorrow.

[joanhey]

joanhey @ kumbiaphp.com

[joanhey]

What type of session do you use: file, redis, memcached, ... ?

[joanhey]

In Workerman 4 we can use more session types, but not in v3.5

[mouyong]

redis

[joanhey]

So I'll need to check the redis code in Laravel for now.
The session is the part, that I never used before for my API's and microservices.
So we need to fix more the session.

[joanhey]

And like before, we can create a Workerman session than don't need Redis.
Workerman is as fast as Redis.

[mouyong]

already send mail to you.

[joanhey]

Remember that the Eloquent ORM is very slow. Also when use it with Workerman.

[mouyong]

ok, have some suggest give me?

[mouyong]

Sorry, Maybe i need to sleep.in tommorrow i will be see your Leaving a message.

[joanhey]

OK, see you tomorrow.

But Adapterman use Workerman v3.5, and in this version the session is fixed to filesystem.
But we can work to change it.

[joanhey]

Try temporally to use the default filesystem session.
To test that it's working with Adapterman.

[joanhey]

Some apps will not work with Workerman, but also not with Octane.
Because use global or static variables, that in a persistent app are never destroyed or cleaned.

[joanhey]

If you only use 1 server, you don't need Redis.
The use of Redis or Memcache, it is not for performance but for manage multiple app servers.

In Linux, using filesytem session, that session files will end up in Linux Filesystem Cache (RAM). Also normally the session use more read than write.
Or it's possible to force to use ram using TMPFS.
Example article:
https://eddmann.com/posts/storing-php-sessions-file-caches-in-memory-using-tmpfs/

[joanhey]

After test your app, the session is working with redis too.
But there is a strange behavior with the logout, that I'm checking to fix.

[mouyong]

hello, in my app, use fpm, it can successful, in workerman, it run failed. i can't know different before php-fpm and workerman cli. I already fix a application error. now it can run in php-fpm mode.