Start and configure

Engine does not open a socket by itself. support\App::run() reads the server configuration, registers the primary listener and configured servers/process entries, then calls localzet_start() and Server::runAll().

Listener configuration

Triangle Full uses config/server.php. This shortened example reflects that configuration shape:

<?php

return [
    'name' => env('APP_NAME', 'Triangle App'),
    'count' => env('SERVER_COUNT', cpu_count() * 4),
    'listen' => env('SERVER_LISTEN', 'http://127.0.0.1:8000'),
    'handler' => Triangle\Http\App::class,
    'constructor' => [
        'requestClass' => Triangle\Request::class,
        'logger' => support\Log::channel(),
        'basePath' => run_path(),
        'appPath' => run_path('app'),
        'configPath' => run_path('config'),
        'publicPath' => run_path('public'),
        'runtimePath' => run_path('runtime'),
    ],
    'master' => [
        'pidFile' => 'triangle.pid',
        'statusFile' => 'triangle.status',
        'stdoutFile' => 'logs/stdout.log',
        'logFile' => 'logs/server.log',
    ],
];

This is an example from Triangle Full, not a configuration generated by Engine. The handler and its dependencies must exist in the application. Set process count, bind address, TLS context, user, and runtime paths for your deployment.

Additional endpoints and processes

On Unix, Engine combines servers and process arrays from application and plugin configuration. It forwards endpoint properties such as listen, count, protocol, transport, server, handler, constructor, and services to localzet_start().

If GLOBAL_START is defined, Engine registers endpoints but does not invoke Server::runAll(). The application launcher must then start the shared runtime.

Verify startup

Use the commands provided by the Triangle project and verify the Server status, bind address, worker processes, and logs. Server runtime commands are documented in the runtime guide.