Search by

ske-io / php-bridge

ske-bot

Runs PHP applications on SKE: HTTP, queues and console

Package info

github.com/ske-io/bridge-php

pkg:composer/ske-io/php-bridge

Security

Advisories: 0

Aikido package health analysis

Transparency log

Statistics

Installs: 11

Dependents: 0

Suggesters: 0

Stars: 0

Open Issues: 0

v0.2.1 2026-11-06 20:02 UTC

Requires

  • php: ^8.3

Requires (Dev)

Suggests

  • aws/aws-sdk-php: Required on AWS for the default ske queue connection, which sends jobs to SQS.
  • inertiajs/inertia-laravel: Required only for applications opting into Inertia SSR.
  • laravel/framework: Laravel 11, 12 or 13. The bridge integrates with it automatically when it is installed.
  • laravel/octane: Required at ^2.22 in production dependencies when enabling Octane HTTP execution on AWS.

Provides

None

Conflicts

Replaces

None

MIT 8fda80c7e97d1724b5c9ec03f816f7a5f6468a09

Published on Packagist.org on 2026-11-08 21:22 UTC

This package is auto-updated.

Last update: 2026-11-08 21:22:28 UTC

README

ske-io/php-bridge runs a Laravel application on SKE, which deploys it into your own AWS or GCP account. It connects the application's HTTP requests, queued jobs, commands and scheduler to the platform.

Requirements

  • PHP 8.3 or later
  • Laravel 11, 12 or 13

Installation

composer require ske-io/php-bridge

Laravel discovers the service provider, so there is nothing to register or configure. Off the platform the bridge stays inactive, apart from the upload endpoint, so the same application runs locally as before.

On AWS, the platform's queue connection sends jobs to SQS through the AWS SDK, which the bridge doesn't require. Install it if the application doesn't have it yet:

composer require aws/aws-sdk-php

What it does on the platform

  • Queues: adds the ske queue connection (SQS on AWS, Cloud Tasks on GCP) and runs the jobs the platform delivers, recording failures in the application's failed jobs store.
  • Logs: writes logs to stderr, one JSON line per record, so the platform's log viewer shows level, message, context and exception.
  • AWS credentials: lets the AWS SDK use the function role's temporary credentials. A key pair the application sets itself still wins.
  • Mail: sends SES mail from the region of the mail provider linked to the environment.
  • Maintenance mode: follows the maintenance mode set in the SKE dashboard. Visitors with the MAINTENANCE_MODE_SECRET bypass cookie and requests from addresses on the environment's access list still reach the application. The platform marks those requests with a header carrying a secret token that it puts in SKE_MAINTENANCE_BYPASS_TOKEN when the instance starts; a request is let through only when the two match, and never when the token is unset. See Maintenance mode.
  • Encrypted environment file: loads the environment's .env.{environment}.encrypted when its key is set. See Encrypted environment file.
  • Inertia SSR: when SSR is turned on for the environment, sends Inertia's render calls to the platform's SSR server. This needs inertiajs/inertia-laravel.

Client address and proxies

The bridge trusts no proxy. On the platform the request reaches Laravel over HTTPS on its real host, from the address that connected to the platform, so Request::ip() and url() are right with no configuration, as behind nginx on a server. Behind a CDN such as Cloudflare, that address is the CDN's: trust the CDN's published ranges with $middleware->trustProxies(at: [...]) in bootstrap/app.php, never *. See Behind a CDN or proxy.

Laravel Octane

Octane is an optional HTTP execution mode on AWS Lambda. Install it as a production dependency:

composer require 'laravel/octane:^2.22'
ske settings runtime octane=true
ske deploy

This mode supports Laravel 11–13 and PHP 8.3–8.5. Laravel stays booted between HTTP requests. Queues, scheduled tasks, and Artisan commands keep their existing execution paths. PHP-FPM remains the default when Octane is disabled.

The bridge captures each response, runs termination callbacks and Octane cleanup, and only then returns the response to the platform. A lifecycle failure fails the invocation and discards the worker; the platform does not replay the request. Application side effects may already have occurred. Workers also retire after 250 requests by default; set a positive octane-max-requests runtime setting to change the limit.

Forms, sessions, cookies, nested uploads, and downloads retain their Laravel behavior. Finite streamed responses are buffered while their request context is active. Platform body limits and deadlines apply; live streaming and SSE are unavailable. The platform parses multipart requests and owns temporary upload files until the request lifecycle completes. No multipart-parser package is required in the application.

Applications must follow Laravel's Octane compatibility guidance: do not retain request-specific state in static variables or long-lived singletons. This mode does not run Swoole, RoadRunner, or FrankenPHP servers. Server-specific task workers, shared tables, timers, and Octane server management commands are unavailable; use queues and scheduled tasks for durable background work.

Cloud Run is not supported by this mode yet.

Documentation

Development

composer install
vendor/bin/pint --test
vendor/bin/phpstan analyse
vendor/bin/pest

License

The MIT License. See LICENSE.