Libraries tagged by new line

A Twitch API package for laravel, providing features like dual-api (new helix and v5 kraken), easy authentification and automatic user-assignment

Go to Download

Helpful tools for working with the new d.velop utils like d.3one, d.ecs http gateway and d.velop cloud. This tool is still under development!

Go to Download

WDB is the fast, easy and versatile PHP ORM. It allows you manage databases with ease and efficiency. In a few words: MIT license, PHP 5.3 or newer, familiar syntax, zero hassle, zero configuration, easy to use, simple to learn, flexible, fast, powerful and smart, mysql, postgresql, sqlite, sqlserver, oracle, etc.

Go to Download

CalameoBundle add a new field type to ezplatform to link content to calaemo

Go to Download

a new concept of mailto and tel links

Go to Download

Upload your silverstripe e-commerce products to TradeMe (New Zealand version of E-Bay and the like).

Go to Download

Magento 2 Product Labels extension allows store owner to display different labels like the Hot (Best Seller), Sale, Featured, New labels on product view and category view.

Go to Download

Customer Attributes extension helps the store owner to manage and add new customer attributes. By using Customer attributes extension, store owner can create additional fields on the customer account register page, customer account edit page and admin manage customers. The objective of using this extension is to collect business-related and personal information that the store owner needs from the customer. A store owner can create an unlimited number of additional input fields like text box, text area, Date, Yes/No, Dropdown etc. The store owner can set default value & input validation for attributes. A store owner can add the attribute to the list of column options and list of filter options in the customer grid from admin.

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

Interactive Park Planner is a TYPO3 extension which is using leaflet library to place and show markers with its description on an image. You can create as many "plans/images" as you want. Markers with custom icons can also be used. Also, per marker, you can define individual titles and links to subpages. - Get in touch with us: Open New Media GmbH | Digital communication agency | Tel .: +49 261 30380-80 | E-Mail: [email protected] | Web: https://www.onm.de | Hotel solutions: https://www.hotelsuite.de

Go to Download

hotelsuite FORM (hs FORMS) will show a form to book hotel rooms with some customized configurations. This plugin allows the creation of deep links and booking buttons in connection with the Internet booking engine "hotelsuite IBE" (https://www.hotelsuite.de). Sell rooms, vouchers, events, tables and much more! - Get in touch with us: Open New Media GmbH | Digital communication agency | Tel .: +49 261 30380-80 | E-Mail: [email protected] | Web: https://www.onm.de | Hotel solutions: https://www.hotelsuite.de

Go to Download

T3 New Age Landing TYPO3 Template is a Bootstrap minimal app landing page. This template has been designed for any need to showcase app or website, app landing page. Built it with twitter bootstrap 3, HTML5, CSS3 and SASS. Live-Demo: https://demo.t3planet.com/?theme=t3t-newage Pro-Version & Support: https://t3planet.com/t3-new-age-landing-typo3-template

Go to Download

Experience personalized shopping like never before with our personal shopping module. Simply schedule an appointment with one of our expert stylists who will curate a tailored selection just for you, ensuring great fit and awesome new styles

Go to Download

Experience personalized shopping like never before with our personal shopping module. Simply schedule an appointment with one of our expert stylists who will curate a tailored selection just for you, ensuring great fit and awesome new styles

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