Libraries tagged by one-app
jhancock/yii2-version-assetmgr
26563 Downloads
Yii2 asset manager that hashes based on application version instead of mtime. Useful for load balanced sites.
vortos/vortos-audit
1490 Downloads
Vortos Audit — enterprise-grade unified audit spine. One append-only, hash-chained, per-scope/per-tenant event store with controlled action vocabulary, sensitivity classification, impersonation-chain capture, async (Kafka) ingestion, partitioned storage, retention + cold-storage tiering, keyset query, and signed per-tenant export. Replaces per-app hand-rolled audit tables.
envor/one-app
4244 Downloads
Database per team starter kit for Laravel based on Laravel Jetstream and Livewire
nickaguilarh/holo-constraints
2654 Downloads
A package that allow entities to have constraints on app level.
webkul/code-generator
2401 Downloads
module lets you generate models, controller, helpers in seconds so that you can focus more on application logic
ali-translator/buffered-translation
1582 Downloads
Manually pasted text on document for translation, by means of buffering is translated by one approach (helpful for DB sources)
lizhichao/one-app
1053 Downloads
一个极简的php框架,可运行在fpm或者swoole协程模式下
sloukapetr/laravel-cookie-consent
18 Downloads
Multi-site cookie consent for Laravel: one app, many hostnames, separate consent per domain.
azzarip/domains
82 Downloads
Modularize Laravel domains in one app
xp-framework/remote
41099 Downloads
Remote method invocation on Application Servers
paypaplane/svix-client
24611 Downloads
Welcome to the Svix API documentation! Useful links: [Homepage](https://www.svix.com) | [Support email](mailto:[email protected]) | [Blog](https://www.svix.com/blog/) | [Slack Community](https://www.svix.com/slack/) # Introduction This is the reference documentation and schemas for the [Svix webhook service](https://www.svix.com) API. For tutorials and other documentation please refer to [the documentation](https://docs.svix.com). ## Main concepts In Svix you have four important entities you will be interacting with: - `messages`: these are the webhooks being sent. They can have contents and a few other properties. - `application`: this is where `messages` are sent to. Usually you want to create one application for each user on your platform. - `endpoint`: endpoints are the URLs messages will be sent to. Each application can have multiple `endpoints` and each message sent to that application will be sent to all of them (unless they are not subscribed to the sent event type). - `event-type`: event types are identifiers denoting the type of the message being sent. Event types are primarily used to decide which events are sent to which endpoint. ## Authentication Get your authentication token (`AUTH_TOKEN`) from the [Svix dashboard](https://dashboard.svix.com) and use it as part of the `Authorization` header as such: `Authorization: Bearer ${AUTH_TOKEN}`. For more information on authentication, please refer to the [authentication token docs](https://docs.svix.com/api-keys). ## Code samples The code samples assume you already have the respective libraries installed and you know how to use them. For the latest information on how to do that, please refer to [the documentation](https://docs.svix.com/). ## Idempotency Svix supports [idempotency](https://en.wikipedia.org/wiki/Idempotence) for safely retrying requests without accidentally performing the same operation twice. This is useful when an API call is disrupted in transit and you do not receive a response. To perform an idempotent request, pass the idempotency key in the `Idempotency-Key` header to the request. The idempotency key should be a unique value generated by the client. You can create the key in however way you like, though we suggest using UUID v4, or any other string with enough entropy to avoid collisions. Svix's idempotency works by saving the resulting status code and body of the first request made for any given idempotency key for any successful request. Subsequent requests with the same key return the same result. Please note that idempotency is only supported for `POST` requests. ## Cross-Origin Resource Sharing This API features Cross-Origin Resource Sharing (CORS) implemented in compliance with [W3C spec](https://www.w3.org/TR/cors/). And that allows cross-domain communication from the browser. All responses have a wildcard same-origin which makes them completely public and accessible to everyone, including any code on any site.
mhnassar/multi-tenant
21 Downloads
MultiTenant package / one application with multi databases schema
vkoori/one-app
3 Downloads
A minimalist php framework that can run in fpm or swoole coroutine mode
luceos/on-app
932 Downloads
OnApp external PHP wrapper changed into a composer version
nim/nim-application
12 Downloads
Ngo Information Management