Libraries tagged by Domain Move

bean-component/php-thing

0 Favers
1543 Downloads

Provides a Component for Thing Domain Model.

Go to Download


bean-component/php-organisation

0 Favers
35 Downloads

Provides a Component for Organisation Domain Model.

Go to Download


bean-component/php-geolocation

0 Favers
31 Downloads

Provides a Component for Geolocation Domain Model.

Go to Download


riconet/typo3-order

0 Favers
15 Downloads

This extension provides a simple cart functionality. You can add domain model objects, by using a partial in your templates, to the cart and create orders.

Go to Download


kambalabs/kmb-zend-db-infrastructure

0 Favers
791 Downloads

Kamba core module that provides a Zend DB implementation of all repositories of domain models

Go to Download


kambalabs/kmb-memory-infrastructure

0 Favers
174 Downloads

Kamba module that provides a Memory implementation of all repositories of domain models (useful for tests)

Go to Download


yoghi/madda

0 Favers
0 Downloads

Model And Domain Driven Architecture

Go to Download


tuzex/ddd-shared-kernel

0 Favers
21 Downloads

Shared model for Domain Driven Design (DDD) project in PHP

Go to Download


maymeow/cakephp-service-layer

0 Favers
1164 Downloads

Service layer and domain / business model implementation for CakePHP

Go to Download


sillynet/adretto

0 Favers
77 Downloads

Write modern PHP (Action-Domain-Responder) in Wordpress themes.

Go to Download


ru-tld/yii2-asset-qq

2 Favers
31 Downloads

QQ.domains asset files: images, configs and more

Go to Download


lbhurtado/missive

0 Favers
562 Downloads

Add SMS domain to a Laravel project - route, models, migrations, jobs, notifications, etc.

Go to Download


ecentria/ecentria-apievents-bundle

1 Favers
3487 Downloads

Generic consumer and standard event message model meant to pull in a domain event message from rabbitmq and repeat it as a symfony event to all listening services

Go to Download


piurafunk/docker-php

0 Favers
8 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.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


maxvaer/docker-openapi-php-client

0 Favers
4 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.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


<< Previous Next >>