Libraries tagged by prediction

Mezzanine is a Laravel4 package for easy asset management. His main feature is to provide a dual source management to each asset, meaning you can use a local file for your developpment needs, then use a faster CDN source for production, without modifying your code.

Go to Download

Did you implement a language file after your on production? Then you know its hard to determine if your caught every string. This package implement's a console command change every (or selected) values of a language file to emojis or a predefined string to rapidly identify any loose ends.

Go to Download

Form renderer for Bootstrap CSS framework. This is early stage of production, use on YOUR OWN RISK.

Go to Download

A simple router. Not designed to be used in production.

Go to Download

This is a simpler helpers classes to create a better web application using php. This is intentend to be use for devlopment only for learning purpose using xampp or others. This provides routing,data passing, separation of code using mvc pattern. This is not optmize for production level. Its only for beginner who don't want to use library like laravel or etc

Go to Download

Production console commands for photobank-backend

Go to Download

Laravel chart production helper for Hightcharts

Go to Download

Sanitize user data after cloning a database to non-production environments.

Go to Download

Citadel - A production-ready Laravel backend boilerplate with OAuth2, permissions, media management, full-text search capabilities, and interactive admin commands.

Go to Download

Mutes deprecation logs in production

Go to Download

Auditor Framework preAlpha version to get a Production version go to TheCodeFigthers

Go to Download

Laravel badwords filter package (multi-language, production-ready)

Go to Download

Email notify about errors and exceptions happened in production mode

Go to Download

Mapping of files that should be cloned to the production servers

Go to Download

The Nodeum API makes it easy to tap into the digital data mesh that runs across your organisation. Make requests to our API endpoints and we’ll give you everything you need to interconnect your business workflows with your storage. All production API requests are made to: http://nodeumhostname/api/ The current production version of the API is v1. **REST** The Nodeum API is a RESTful API. This means that the API is designed to allow you to get, create, update, & delete objects with the HTTP verbs GET, POST, PUT, PATCH, & DELETE. **JSON** The Nodeum API speaks exclusively in JSON. This means that you should always set the Content-Type header to application/json to ensure that your requests are properly accepted and processed by the API. **Authentication** All API calls require user-password authentication. **Cross-Origin Resource Sharing** The Nodeum API supports CORS for communicating from Javascript for these endpoints. You will need to specify an Origin URI when creating your application to allow for CORS to be whitelisted for your domain. **Pagination** Some endpoints such as File Listing return a potentially lengthy array of objects. In order to keep the response sizes manageable the API will take advantage of pagination. Pagination is a mechanism for returning a subset of the results for a request and allowing for subsequent requests to “page” through the rest of the results until the end is reached. Paginated endpoints follow a standard interface that accepts two query parameters, limit and offset, and return a payload that follows a standard form. These parameters names and their behavior are borrowed from SQL LIMIT and OFFSET keywords. **Versioning** The Nodeum API is constantly being worked on to add features, make improvements, and fix bugs. This means that you should expect changes to be introduced and documented. However, there are some changes or additions that are considered backwards-compatible and your applications should be flexible enough to handle them. These include: - Adding new endpoints to the API - Adding new attributes to the response of an existing endpoint - Changing the order of attributes of responses (JSON by definition is an object of unordered key/value pairs) **Filter parameters** When browsing a list of items, multiple filter parameters may be applied. Some operators can be added to the value as a prefix: - `=` value is equal. Default operator, may be omitted - `!=` value is different - `>` greater than - `>=` greater than or equal - `=` lower than or equal - `>

Go to Download