Libraries tagged by file protection
mykehowells/dotenv
9623 Downloads
Load .env file into project environment, using same functions as Laravel
uziiuzair/secure-env-php
146 Downloads
Encrypt environment files for production use.
pvsv1984/secure-env-php
472 Downloads
Encrypt environment files for production use.
nishant-sharma/secure-env-php
5 Downloads
Encrypt environment files for production use.
igsem/api-exceptions
76 Downloads
Handle exceptions in Phalcon or other PHP APIs in a consistent way. Return consistent responses with proper response codes and have your errors and exceptions be logged into file on production.
pkeogan/laravel-lang-tester
1 Downloads
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.
drupal/clean_package
7 Downloads
A composer cleanup plugin, to keep only production required package files and maintain better security level.
cmskit/lib-openlayers
624 Downloads
Openlayers as a production bundle without any development files like tests etc..
cmskit/jquery-ui
151 Downloads
jQuery and jQuery UI JavaScript libraries as a production bundle without any development files like tests etc..
backfron/laravel-inline-assets
71 Downloads
Render your javascript and css files inline for better performance in production.
oktopost/dep-map
32 Downloads
Mapping of files that should be cloned to the production servers
seekgeeks/cssjsminify
70 Downloads
CSS JS minify tool will help in minification of your entire js/css file and put in directly from where you can use it in production build. with simple command you can minify all static c content like stylesheets and javascripts to production ready code
plateau/mezzanine
22 Downloads
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.
nodeum-io/nodeum-sdk-php
0 Downloads
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 - `>
jeontwikkeling-nl/ltisaas_client_api_php
24 Downloads
A brief overview of the API versions: v0: This version is solely for testing and does not interact with the database, nor does it involve any validation. It simply serves mock data. v1: This is the official version of the LtiSaas API, intended for production use. Please be informed that when testing version v0, the HTTP Access-Token header should be set with the value 'dummy'. Also, please note that the API has a limit of 2500 results per response. Additionally, all webservices support both POST and GET requests. However, the POST method is required when uploading files.