Libraries tagged by html engine
comely-io/knit
664 Downloads
Knit — official Comely HTML templating engine
devgroup/bh
542 Downloads
Template engine. BEMJSON -> HTML processor. PHP port of https://github.com/bem/bh
vanilla/ebi
381 Downloads
A template engine made with HTML.
phoxy/clap
21 Downloads
Make html snapshot for search engines
page-carbajal/wpexpress-ui
3 Downloads
HTML Helper and Render Engine for WPExpress.
nowshad/inflater
5 Downloads
This is a template engine to parse html templates like Jinja template engine used in Python Flask
jmvdevelop/nodi
73 Downloads
A template engine to render html tree
diversity_templating/diversity-php
2747 Downloads
Engine for generic HTML components
ziimple/grypthon
104 Downloads
Grypthon is a templating engine for easy HTML deployment inspired from React to allow a more declarative approach to website on server side./
canteen/parser
1054 Downloads
Simple engine for rendering HTML templates.
iamine/blader
12 Downloads
HTML Generator using Laravel Blade templating engine
awisoft-net/ginger-jinga
8 Downloads
This is another update for simple template engine to render front end html pages for default
dino/dompdf
665 Downloads
A PDF engine that generates PDFs based on HTML code.
volta-framework/component-template
20 Downloads
A HTML - PHP template module based on the PHP build in template engine.
matthewbaggett/docker-api-php-client
6 Downloads
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.43) is used. For example, calling `/info` is the same as calling `/v1.43/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 [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (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..." } ```