Libraries tagged by sharp

rezozero/social-links

15 Favers
4793 Downloads

Provide social network url for sharing.

Go to Download


quasarstream/mixin

0 Favers
643 Downloads

This library builds upon common PHP classes and traits shared across the WebRTC ecosystem.

Go to Download


quasarstream/av

0 Favers
595 Downloads

This PHP library leverages the Foreign Function Interface (FFI) to directly interact with native FFmpeg shared libraries (libavcodec, libavfilter, libavformat, etc.), providing low-level access to powerful multimedia processing capabilities within PHP.

Go to Download


presta/sonata-saved-filters-bundle

0 Favers
3811 Downloads

A Symfony bundle to allow user to save and share filters in Sonata Admin

Go to Download


placetopay/magento2-module-payments

1 Favers
6719 Downloads

Shared component for accepting online payments in Magento 2 using the PlacetoPay payment gateway.

Go to Download


phpgenesis/common

0 Favers
3903 Downloads

Shared Functionality for PHPGenesis

Go to Download


pflorek/aws-paramstore

5 Favers
9345 Downloads

This library reads parameters from AWS Parameter Store. It supports a path prefix, an optional shared context and multiple profiles. Returns an multi dimensional array of string|int|float|bool. Integrates directly with zendframework/zend-config-aggregator.

Go to Download


permafrost-dev/phpcsfixer-preset

22 Favers
5843 Downloads

shared php-cs-fixer rules & finders preset

Go to Download


paypaplane/svix-client

0 Favers
14197 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.

Go to Download


omeka/omeka-s

436 Favers
48 Downloads

The Omeka S collections management system. A local network of independently curated exhibits sharing a collaboratively built pool of items and their metadata.

Go to Download


myparcelcom/json-api

0 Favers
70832 Downloads

MyParcel.com shared library with JSON API related exceptions, interfaces, traits and utility classes.

Go to Download


morozovsk/websocket-examples

38 Favers
2062 Downloads

examples for simple php websocket server: simple chat (single daemon) - http://sharoid.ru/chat.html , pro chat (master + worker) - http://sharoid.ru/chat2.html , simple game - http://sharoid.ru/game.html

Go to Download


mll-lab/rector-config

0 Favers
23580 Downloads

Shared rules for Rector

Go to Download


microweber-deps/laravel-cors

1 Favers
58000 Downloads

Fork of fruitcake/laravel-cors Adds CORS (Cross-Origin Resource Sharing) headers support in your Laravel application

Go to Download


manish-pareek/stack-cors

0 Favers
8456 Downloads

Cross-origin resource sharing library and stack middleware

Go to Download


<< Previous Next >>