Libraries tagged by drone

Advanced console util that make pukoframework get things done on the fly.

Go to Download

Imports a ProjectSend v1 (r2098-era) install — database and files — into ProjectSend v2. Installed on demand, removed when the migration is done.

Go to Download

Liveblogging done right. Using WordPress.

Go to Download

This autoloader supports every autoloadable PHP feature up to PHP 5.4’s traits. It find’s every class, interface or traits definition in any situation. No matter what convention is used. The autoloader is index based. After building the index there will be no performance issue. The building is done dynamically. There is no explicit need of calling a build script. For the sake of comfortability there exists a script for prebuilding an index.

Go to Download

Laravel route binding, done right.

Go to Download

Laravel route binding, done right.

Go to Download

Collection base classes that do not depend on other non-collection packages, on which there is a dependency of other collection packages that depend on this package. This is done to avoid circular reference in the collection toolchain

Go to Download

Quick way to save jobs that have been created without any problem. The antithesis of failed jobs.

Go to Download

Package to help with filtering/search/sort in queries

Go to Download

A package to simplify serialization management.

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. List endpoints additionally take a `?brandScope=own|shared|both` parameter to narrow further within whichever brand context already applies. `own` returns only rows assigned to that brand, and requires a brand context — a brand-bound token, a resolved brand session, or the `X-Zippendo-Brand` header above — otherwise `400`. `shared` returns only the organization-wide rows (equivalent to filtering `brandId=none`). The default, `both`, keeps the existing behaviour: a brand context sees its own rows plus the organization-wide ones. Set `X-Zippendo-Brand-Scope` as a client default to apply the same choice to every request instead of repeating the query parameter on each call — an explicit `brandScope` query parameter always wins over the header, and a blank header value is ignored. 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

Allows to show the first post of a topic on top of its every page. This can be done by checking the relevant checkbox in the post options while creating a new topic or editing the first post of existing one. Also, you can set the first post to be always on top of every topic on per-forum basis by setting the relevant option on forum admisitration page (while creating a forum or editing settings for existing forum).

Go to Download

Nythros 游戏框架层（Game framework layer）：三基类（BasePlayer/BaseMonster/BaseNPC，继承 engine 的 Actor\BaseActor）+ 战斗模块（Combat/CombatService + MonsterActor + DropEntity/DropTable + EntityTypeIndex）+ 背包（Inventory）+ 社交模块（Social/SocialService + Team/Guild/Location 存储）+ 玩家 Actor（Actor/PlayerActor）+ 身份（Auth/Identity）+ 插件机制（PluginInterface/PluginRegistry + Skill/Item/Buff 官方插件）+ 实时服务器运行时（Server/RealtimeServer + ConnectionRegistry + FrameMerger）+ 部署（Deploy/DeployConfig）+ 观测（Observability/PerfSampler）+ 持久化管道（Persistence/ArchivePipeline）。

Go to Download

Laravel localization done right.

Go to Download

Get a multiple file AJAX upload done in minutes

Go to Download