Adapterman

When you run ./vendor/bin/adapterman start, the following process occurs:

1. The binary executes a PHP script with a custom configuration: /usr/bin/env php -c vendor/joanhey/adapterman/cli-php.ini vendor/joanhey/adapterman/src/start.php "$@".
2. The -c vendor/joanhey/adapterman/cli-php.ini flag applies a specific PHP configuration. This configuration disables certain built-in PHP functions, which the Adapterman framework then re-implements. This ensures that functions that typically behave differently under FPM work correctly under the PHP CLI.
3. The vendor/joanhey/adapterman/src/start.php script handles the server startup and performs automatic framework detection (referencing logic found in vendor/joanhey/adapterman/src/frameworks/index.php).

After installation, you can start the server using the Adapterman CLI binary. The server automatically detects the framework being used (e.g., ThinkPHP) and starts the appropriate environment. Once running, the application is accessible at http://localhost:8080.

./vendor/bin/adapterman start

Once you have configured your start.php file with the required run() function and global $app variable, you can start the server using the server.php command.

By default, the application will be accessible at http://localhost:8080.

php server.php start

To integrate Adapterman into your ThinkPHP project, use Composer to require the package. This adds the necessary Adapterman files to your vendor directory.

composer require joanhey/adapterman

Once server.php and start.php are configured, start the application from the project root using the PHP CLI. The server will be accessible at the host and port defined in server.php (defaulting to http://localhost:8080).

php server.php start

When using Laravel with Adapterman, you must modify the start.php file (copied from public/index.php) to wrap the Laravel kernel handling inside a run() function. This function uses output buffering (ob_start() and ob_get_clean()) to capture the application response so it can be sent back through the Workerman connection.

<?php

$app = require_once __DIR__.'/bootstrap/app.php';

global $kernel;

$kernel = $app->make(Illuminate\Contracts\Http\Kernel::class);

function run()
{
    global $kernel;

    ob_start();

    $response = $kernel->handle(
        $request = Illuminate\Http\Request::capture()
    );

    $response->send();

    $kernel->terminate($request, $response);
    
    return ob_get_clean();
}

Install Adapterman using Composer. This command will also automatically install the Workerman dependency.

composer require joanhey/adapterman

Once you have created and modified your start.php file, you can start the Workerman server using the server.php CLI tool.

php server.php start

Once you have created your adapted start.php file, you can launch the application using the server.php command. By default, the application will be accessible at http://localhost:8080.

php server.php start

You can use Nginx to handle TLS termination, serve static files, and proxy requests to your Workerman-based applications under the same domain.

To set this up, configure an Nginx server block that serves your static files from a public directory and uses a location @backend block to proxy all other requests to your application's IP and port.

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

    # Change to your public dir
    root /var/www/html/your-app/public;
    index index.html index.htm;

    server_name localhost;

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

    # Add the ip:port of your app
    location @backend {
         proxy_pass 127.0.0.1:8080; // or localhost:8080;
         proxy_http_version 1.1;
         proxy_set_header Connection "";
    }

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

When adapting app/index.php to a Workerman-compatible start.php, follow these steps:

1. Disable runtime limit adjustments: Comment out or remove set_time_limit(0) and ini_set('memory_limit', ...) calls. It is recommended to set these values directly in your php.ini instead.
2. Global Kernel: Declare the $kernel as a global variable and instantiate it outside the request loop.
3. Implement run() function: Create a run(): string function that:
   • Uses ob_start() to begin output buffering.
   • Creates the request using Request::createFromGlobals().
   • Handles the request via $kernel->handle($request).
   • Sends the response via $response->send().
   • Terminates the request via $kernel->terminate($request, $response).
   • Returns the captured output using ob_get_clean().