Libraries tagged by mock data

A laravel libery for encription data and url.

Go to Download

Package to create simple seeders with ability to lock/unlock tables

Go to Download

Preview pending migration impact — row counts, lock estimates, and risk ratings — before you run migrate.

Go to Download

Ensure Laravel queue jobs run on only one server instance at a time with database or Redis distributed locking, heartbeat, and crash recovery.

Go to Download

Rock Symphony Propel is an open-source Object-Relational Mapping (ORM) for PHP.

Go to Download

Date Calc and Format Tools for php 5.1.6

Go to Download

Database Orm Tools for php 5.1.6

Go to Download

Database Abstraction Layer for php 5.1.6

Go to Download

Plugin to lock database rows using the CakePHP ORM

Go to Download

Reliable wp-cron for WordPress on more than one server: in-process through WP-CLI, a single runner elected by a shared database lock, and loud when it stalls.

Go to Download

Laravel package to lock an app after x - date.

Go to Download

A PHP security checker for your composer.lock with github/advisory-database

Go to Download

Provides an interface to manage database locks and keep a lock active by Ajax request

Go to Download

Sequential order numbers for Craft Commerce — real counters with prefixes, padding, date tokens and periodic resets, allocated under a lock so two checkouts can never share a number.

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.40) is used. For example, calling `/info` is the same as calling `/v1.40/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a Base64 encoded (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download