Download the PHP package webong/proxy without Composer
On this page you can find all versions of the php package webong/proxy. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package proxy
Short Description Framework-neutral HTTP profiles, TCP/UDP proxy transports and storage-neutral registry contracts.
License MIT
Informations about the package proxy
Proxy
webong/proxy is a Laravel package for registry-backed webhook endpoints and
outbound HTTP client profiles. An endpoint is a durable network identity: it
can receive and route webhooks through subscriptions, and it can own named
outbound profiles for clients such as Guzzle.
Install
Laravel discovers Webong\Proxy\WebProxyServiceProvider automatically.
Publish the package configuration and normal migrations, then migrate:
The normal migration set creates:
endpointssubscriptionsendpoint_registrationsprofiles
All table names are configurable in config/proxy.php or through the matching
PROXY_*_TABLE environment variables.
Configuration
The package config is config/proxy.php and is read through the proxy.*
namespace. Common environment variables are:
The built-in local registry uses the database driver and provider. Custom
registries can supply their own endpoint driver and provider through
proxy.registries and proxy.providers.
Endpoints
Create or retrieve an endpoint through EndpointRegistry. The endpoint key is
the stable public identity, while client selects the webhook router that
handles incoming work.
An endpoint is not limited to webhook subscriptions. It is the registry-owned parent for all endpoint attachments, including outbound profiles.
Webhook subscriptions
Attach destinations when an inbound webhook route should dispatch to an HTTP request, event, or job:
The package uses the configured channel and registry to resolve the endpoint,
match an incoming route, and dispatch active subscriptions. Delivery options
such as queue name, retries, backoff, idempotency TTL, and failure logging are
configured under proxy.*.
Registry-backed Guzzle profiles
Profiles belong to an endpoint and are persisted by that endpoint's registry. They are not global configuration entries. This lets each endpoint have its own egress identity and keeps profile credentials in the registry store.
GuzzleClientFactory accepts Guzzle's usual proxy string or per-scheme map,
including the no bypass list. Other Guzzle options belong under options.
Profile configuration is encrypted at rest by the database provider.
Migrating from webong/web-proxy
New applications should use only the normal migration tag. Existing installations that already ran the historical prefixed migrations need one explicit compatibility step before they migrate the renamed package:
The opt-in legacy migration renames the historical prefixed tables and updates
Laravel's migrations table to the new migration names. It is intentionally
not included in proxy-migrations.