Libraries tagged by server 2 server

Microsoft SQL Server Bundle for Symfony 2

Go to Download

Microsoft SQL Server Bundle for Symfony 2

Go to Download

Microsoft SQL Server Bundle for Symfony 2

Go to Download

ReactPHP Server On Lumen 5.2

Go to Download

Microsoft SQL Server Bundle for Symfony 2

Go to Download

json-rpc 2.0 client and server library

Go to Download

Gearman Job Server API integration for Symfony 2

Go to Download

A library to retrieve information from quake master servers and game servers

Go to Download

Symfony 2 bundle, push your google analytics hits from the server

Go to Download

A server side alternative implementation of socket.io in PHP based on Workerman, Support Workerman V5 And PHP 8.2

Go to Download

A persistent oauth google client to solve the OAuth persistency (access/refresh tokens) when using server2server communication

Go to Download

ez-jwt allows you to create JWT tokens for Server2Server authentication on the Google APIs and can be modified to work with other OAuth Services

Go to Download

Symfony bundle which provides OAuth 2.0 authorization/resource server capabilities. This is a fork created for testing purposes and it will be used until the source bundle will support thephpleague/oauth2-server v8.0.

Go to Download

It extends an opportunity to listen a conclusion of a dump function in Symfony 3 and add shortcut for a «dump+die» combination. To run dump-server "php dump-server" . Commands: 1) db - dump var and continue script execution 2) dd - dump var and stop script (via "die" func)

Go to Download

Build a fully custom headless storefront - your own web app, mobile app, or POS - against a single OE Commerce store. Every endpoint below is namespaced under `/api/v1/store/...`. Building admin/back-office tooling instead? See [/docs/admin](/docs/admin). New here? [/guides/store](/guides/store) walks through getting a key, the anonymous cart session, and calling your first endpoints step by step - this page is the field-level reference to come back to afterward. ## Getting Started 1. Click the **Authorize** button at the top of this page. 2. Provide credentials: - **X-Commerce-Key** (always required) - your store's Store Access Key from Backoffice > Settings > Application APIs. `pk_store_...` (publishable) is safe for browser/mobile code; `sk_store_...` (secret) is server-to-server only and is rejected outright if a browser Origin header is present. - **Bearer** (only for endpoints acting on a specific customer - Account, Orders, Wishlists, etc.) - the token from **Auth > register** or **Auth > login**. Once authorized, you can explore and test all available endpoints directly from this interface. ## Anonymous Carts A guest cart is tracked by an `X-Session-Ref` header, not a cookie - the server generates one on your first request and echoes it back on every response after. Keep sending back whatever value you last received. Logging in carries that same cart forward onto the customer's account automatically, with no separate merge step. ## Errors Failures use RFC 9457 Problem Details (`application/problem+json`) with a stable `code` field for programmatic handling, e.g. `store_key_invalid`, `store_key_revoked`, `store_key_scope_denied`, `rate_limited`. A rejected *business* action (e.g. adding fewer than a product's minimum order quantity to the cart) instead comes back as HTTP 200 with `"success": false` and a human-readable `message` - always check `success` in the body, not just the HTTP status code. ## Rate Limits Requests are limited per Store Access Key (200/minute). The credential-stuffing surface (register/login/forgot-password/reset-password) is limited more tightly per caller IP (10 per 5 minutes). A 429 response includes a `Retry-After` header.

Go to Download