Libraries tagged by rar

Ran any language with Spear!

Go to Download

Contains some useful functions made by Ra-Solo developers

Go to Download

Contains some useful functions made by Ra-Solo developers

Go to Download

A simple filesystem based cache in PHP. Ideal for caching large API responses that rarely need updating.

Go to Download

Library used to normalize the structure of files, functions, and classes intended to be ran from a shell.

Go to Download

PHP下RAS数据加密

Go to Download

This behavior for automatic or manual sync data between two models, without declaration relation. This behavior must be attached on master model. Main purposes - for sync rarely modified data from more reliable database storage to redis storage for frequently access; Support actual data state in some development cases;

Go to Download

Queue processing system that allows cron-like processors to be defined and ran using a single script entry point.

Go to Download

Ran any language with Spear!

Go to Download

A simple library that allows you to generate character characteristics depending on their rarity

Go to Download

A patch system designed similar to Laravel's database migration tools. Instead of being used to manage schema, the patch system is used to fill that grey area between a database seeder and a database migration. The intentions of the system is to patch/adjust existing data, but this could be a replacement for seeders since whether a patch has been ran or not is tracked.

Go to Download

RA Tools

Go to Download

# Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact # Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit and the request has been rejected. # Basics ## HTTPS It's required ## URL Prefix In order to maintain version integrity into the future, the API is versioned. All calls currently begin with the following prefix: https://api.statuspage.io/v1/ ## RESTful Interface Wherever possible, the API seeks to implement repeatable patterns with logical, representative URLs and descriptive HTTP verbs. Below are some examples and conventions you will see throughout the documentation. * Collections are buckets: https://api.statuspage.io/v1/pages/asdf123/incidents.json * Elements have unique IDs: https://api.statuspage.io/v1/pages/asdf123/incidents/jklm456.json * GET will retrieve information about a collection/element * POST will create an element in a collection * PATCH will update a single element * PUT will replace a single element in a collection (rarely used) * DELETE will destroy a single element ## Sending Data Information can be sent in the body as form urlencoded or JSON, but make sure the Content-Type header matches the body structure or the server gremlins will be angry. All examples are provided in JSON format, however they can easily be converted to form encoding if required. Some examples of how to convert things are below: // JSON { "incident": { "name": "test incident", "components": ["8kbf7d35c070", "vtnh60py4yd7"] } } // Form Encoded (using curl as an example): curl -X POST https://api.statuspage.io/v1/example \ -d "incident[name]=test incident" \ -d "incident[components][]=8kbf7d35c070" \ -d "incident[components][]=vtnh60py4yd7" # Authentication

Go to Download

A stack of middleware to be ran as a pipeline

Go to Download