Libraries tagged by shanjing
zaengle/craft-sharingintents
4298 Downloads
Generate social sharing intent URLs
lys/php-sharding-pdo
415 Downloads
drupaljedi/css-tree-shaking
20645 Downloads
Helps you to eliminate the portions of CSS you aren't using. Usually should be used to generate AMP pages, where is the fixed limit for maximum styles size.
wrav/simplesharing
17984 Downloads
Simple Sharing generates social media share links within CP entry pages, allowing you to quickly & easily share entries.
leafs/cors
13142 Downloads
Leaf PHP cors config
aerni/social-links
23339 Downloads
Easily generate Social Sharing Links
aboyadzhiev/php-math-parser
37082 Downloads
Simple mathematical expression parser and calculator.
laminas-commons/lmc-cors
13832 Downloads
Laminas MVC module that let you deal with CORS requests
edu-sharing/auth-plugin
5285 Downloads
Plugin to provide authentification via Auth By App with a edu-sharing repository
uvasoftware/scanii-php
39750 Downloads
A pure PHP interface to Scanii, a web based virus scanning engine (https://scanii.com)
sammyaxe/linkedin-api-php-client
2259 Downloads
LinkedIn API PHP SDK with OAuth 2.0 & CSRF support. Can be used for social sign in or sharing on LinkedIn. Examples. Documentation.
rezozero/social-links
4285 Downloads
Provide social network url for sharing.
paypaplane/svix-client
10230 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.
omeka/omeka-s
27 Downloads
The Omeka S collections management system. A local network of independently curated exhibits sharing a collaboratively built pool of items and their metadata.
microweber-deps/laravel-cors
50808 Downloads
Fork of fruitcake/laravel-cors Adds CORS (Cross-Origin Resource Sharing) headers support in your Laravel application