Libraries tagged by separate

dazza-dev/hyn-multi-tenant

0 Favers
137 Downloads

Maintained continuation of hyn/multi-tenant with Laravel 11 support. Run multiple websites on a single Laravel installation while keeping each tenant's data separated.

Go to Download


cognitive/file-system

0 Favers
51605 Downloads

Lite library to work with file system like Composer\Util\Filesystem but separate and so lite

Go to Download


brilliant-packages/nova-relationships-link-list

5 Favers
16137 Downloads

A Laravel Nova field to display relationships as a comma-separated list of links, rather than a full table.

Go to Download


brezel/multi-tenant

0 Favers
2848 Downloads

Run multiple websites using the same laravel installation while keeping tenant specific data separated for fully independant multi-domain setups.

Go to Download


7ute/laravel-provision

0 Favers
1781 Downloads

Migrate provisioning data separately

Go to Download


tomschlick/townhouse

109 Favers
20 Downloads

A Multitenancy package for Laravel that keeps each tenant in a separate database.

Go to Download


techdivision/application

0 Favers
2335 Downloads

A threaded application implementation to allow a separate context for each application.

Go to Download


silverstripe/mobile

35 Favers
9807 Downloads

The mobile module provides detection for mobile devices, and can serve a different SilverStripe theme to them.The module can either use redirection to a separate mobile domain, or serve mobile optimized content under the same URLs.

Go to Download


integratedexperts/robo-git-artefact

21 Favers
84153 Downloads

Package artifact from your codebase in CI and push it to a separate git repo.

Go to Download


zippendo/zippendo-php

0 Favers
18 Downloads

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


vxsoft/laravel-repository

15 Favers
16 Downloads

Laravel Repository is a powerful Laravel package designed to simplify the interaction with Eloquent models by implementing a repository-based architecture. It separates the data persistence logic from the application's business logic, promoting a clean, maintainable, and testable codebase.

Go to Download


vatson/isolated-callback

4 Favers
2424 Downloads

Allows to execute a callback in a separate fork

Go to Download


uttamrabadiya/api-version-manager

13 Favers
648 Downloads

Simplify Laravel API versioning with ease. No more separate controllers—just flexibility, fallbacks, and version-specific components.

Go to Download


sschreier/sschreierpropertiesinseparateareaproductdetailpage

5 Favers
1 Downloads

show the properties in a separate area on the product detail page

Go to Download


sportsgearswag/artwork-vectorizer

0 Favers
20 Downloads

Converts raster artwork into colour-separated, print-ready SVG: one editable layer per ink, snapped to a PMS palette.

Go to Download


<< Previous Next >>