docker: An API client for docker written in Haskell

[ bsd3, library, network ] [ Propose Tags ]

See API documentation below.


[Skip to Readme]
Versions [faq] 0.1.0.0, 0.1.0.1, 0.2.0.1, 0.2.0.2, 0.2.0.3, 0.2.0.4, 0.3.0.0, 0.3.0.1, 0.4.0.0, 0.4.0.1, 0.4.0.2, 0.4.1.0, 0.4.1.1, 0.5.0.0, 0.5.0.1, 0.5.1.0, 0.5.1.1, 0.6.0.0 (info)
Dependencies aeson (>=0.9.0 && <1.1.0), base (>=4.7 && <5), blaze-builder (>=0.4.0 && <0.5.0), bytestring (>=0.10.0 && <0.11.0), containers (>=0.5.0 && <0.6.0), data-default-class (>=0.0.1 && <0.2.0), http-client (>=0.4.0 && <0.5.0), http-types (>=0.9 && <0.10.0), mtl (>=2.0.0 && <3.0.0), network (>=2.6.0), scientific (>=0.3.0 && <0.4.0), text (>=1.0.0 && <2.0.0), time (>=1.5.0 && <1.7.0), tls (>=1.3.7 && <1.4.0), unordered-containers (>=0.2.0 && <0.3.0), x509 (>=1.6.0 && <1.7.0), x509-store (>=1.6.0 && <1.7.0), x509-system (>=1.6.0 && <1.7.0) [details]
License BSD-3-Clause
Copyright BSD3
Author Deni Bertovic <deni@denibertovic.com>, James Parker <jp@jamesparker.me>
Maintainer Deni Bertovic <deni@denibertovic.com>
Category Network
Home page https://github.com/denibertovic/docker-hs
Source repo head: git clone https://github.com/denibertovic/docker-hs
Uploaded by denibertovic at Wed Sep 7 14:52:34 UTC 2016
Distributions NixOS:0.6.0.0
Downloads 4837 total (335 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs uploaded by user
Build status unknown [no reports yet]

Modules

[Index]

Downloads

Maintainer's Corner

For package maintainers and hackage trustees


Readme for docker-0.3.0.1

[back to package description]

An API client for docker written in Haskell

| Master | Dev | | -------| ---- | | master | dev |

Current state

API is still no stable. We're looking to stabilize the API after the next release (0.4.0.0)

Contributing

If you wish to contribute please see any issue tagged with "help wanted". Make sure to submit your PR's against the dev branch.

Please consider filling an Issue first and discuss design decisions and implementation details before writing any code. This is so that no development cycles go to waste on implementing a feature that might not get merged either because of implementation details or other reasons.