Libraries tagged by Work Code

A mixed bag of tricks for the Silvestripe CMS. Most of them will be obsolete in the future, as there a lot of hacks here with CMS code that does not work so well.

Go to Download

A servicelocator compontent which extract from Yii2.0 for every project.once you work on a broken old code,and you can't change it.di container is your best choose!

Go to Download

Backend extension to manage voucher codes for FE users. This works together with tt_products and agency.

Go to Download

This repository contains Saaspose.SDK for PHP source code. This SDK allows you to work with Saaspose REST API in your PHP applications quickly and easily.

Go to Download

This repository contains GroupDocs Assembly Cloud SDK for PHP source code. This SDK allows you to work with GroupDocs.Assembly Cloud REST APIs in your .NET applications quickly and easily, with zero initial cost.

Go to Download

Works with static publisher to deploy website code to serverless edge services

Go to Download

A composer based Drupal 8 project template to work with the Datacom CI/CD code pipelines.

Go to Download

This repository contains Banckle.Helpdesk SDK for PHP source code. This SDK allows you to work with Banckle.Helpdesk REST API in your PHP applications quickly and easily.

Go to Download

This repository contains Banckle.CRM SDK for PHP source code. This SDK allows you to work with Banckle.CRM REST API in your PHP applications quickly and easily.

Go to Download

This repository contains Banckle.Chat SDK for PHP source code. This SDK allows you to work with Banckle.Chat REST API in your PHP applications quickly and easily.

Go to Download

This repository contains Aspose Cloud SDK for PHP source code. This SDK allows you to work with Aspose Cloud REST API in your PHP applications quickly and easily.

Go to Download

This code will simplify or improve your work with html tables.

Go to Download

originally by codedge/laravel-fpdf, edited some work to meet our own requirement

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

This tool helps developers see how popular their code is and how it's being used. It works with Prometheus and Grafana to gather data from Github and create cool visualizations. You can use Grafana to filter and customize the metrics you collect. We hope you find it helpful!

Go to Download