Libraries tagged by continued

Migration style post deployment commands for Laravel

Go to Download

Create command files that will be run once so that you don't have to remember about it.

Go to Download

PHP SDK to consume continuousphp API

Go to Download

Phing tasks for continuousphp

Go to Download

Deploy agent for continuousphp

Go to Download

A symfony bundle that adds process control to the SonataNotificationBundle.

Go to Download

Some extensions to the default SS test structures to allow parametrisation in CI builds, as well as a framework for selenium testing.

Go to Download

Standalone CLI command to detect continuous integration environment and provide unified access to properties of current build

Go to Download

PHP Censor plugin for Telegram

Go to Download

phing commons build stack

Go to Download

ZF2 module to interact with Zoho Subscriptions API

Go to Download

Public API documentation for Zippendo. Authenticate using your API token (Bearer token prefixed with zipp_). **Brands (sub-accounts).** An organization can be split into brands, each keeping its own orders, shipments and configuration separate. There are two ways to scope requests to one brand, and NEITHER changes any request body: 1. **Bind the token.** Create an API token with a `brandId` and every request it makes is confined to that brand — reads filtered, writes stamped. This is the recommended way to give a single brand's team its own credential. 2. **Send the `X-Zippendo-Brand` header.** An organization-wide token can scope an individual request by sending the brand's id or slug in this header. Most SDKs let you set it once on the client so every call inherits it. A brand-bound token that receives an `X-Zippendo-Brand` header naming a different brand is rejected with `403 BRAND_ACCESS_DENIED` — the binding is never widened. Omit both and requests cover the whole organization, which is the behaviour of every existing token. Records that belong to no brand carry `brandId: null`. Configuration (carriers, shipping rules, addresses) with a null brand is organization-wide and remains visible inside every brand; orders and shipments with a null brand are only visible organization-wide. Brands themselves are managed under the **Brands** tag. Retiring a brand is done with `POST /orgs/{orgId}/brands/{brandId}/archive` — permanent deletion is a dashboard-only action, since it is refused while any order, shipment, member or token still references the brand. Brands require a plan that includes them; creating one beyond your plan's limit returns `403`.

Go to Download

A self-contained, configurable knowledge base package for Laravel

Go to Download

This extension allows you to seamlessly integrate academic content from the Elsevier Pure Research Information System (API v524) into your TYPO3 website, displaying publications, projects, datasets, and equipment details. Based on the Vienna Pure extension, our implementation has been specifically optimized to meet the requirements of Leibniz University Hannover, while also being designed for global use and continuous improvement.

Go to Download

Framework-agnostic PHP SDK for the Takealot Marketplace API (sales, offers, transactions, balances, returns, shipments) with continuation-token pagination and 429 retry handling.

Go to Download