A Haskell library for the Docker Engine API
Go to file
Deni Bertovic 2f949cd868 Makes licence year the year of release
According to this it makes sense to just put in the year the software
was initially released. And not have to update the year in the licence
every time.

http://www.contentious.com/2007/01/07/copyright-notice-is-the-year-really-necessary/
2017-10-10 16:37:23 +02:00
examples Updates docs and examples 2017-03-20 11:05:11 +01:00
scripts Adds script for building docs. 2016-09-07 16:45:15 +02:00
src/Docker Makes licence year the year of release 2017-10-10 16:37:23 +02:00
tests Gets rid of NoEntrypoint constructor 2017-03-23 12:03:55 +01:00
.gitignore Gitignore 2017-03-21 00:04:52 +01:00
.travis.yml Update dependencies to work with the stack lts-9 resolver 2017-09-20 00:19:56 -04:00
CHANGELOG.md Bumps version to 0.4.1.0 2017-10-04 01:25:45 +02:00
CONTRIBUTING.md Adds placeholder for contrib doc 2016-09-05 15:49:20 +02:00
docker.cabal Bumps version to 0.4.1.0 2017-10-04 01:25:45 +02:00
LICENSE Makes licence year the year of release 2017-10-10 16:37:23 +02:00
Makefile Updates Makefile 2017-10-04 01:19:39 +02:00
README.md Removes notice of unstable api 2017-10-04 10:21:55 +02:00
Setup.hs initial commit 2014-09-19 19:52:30 +02:00
stack-7.10.yaml Removes duplicate extra-deps 2017-03-24 12:36:36 +01:00
stack-8.0.2.yaml Update dependencies to work with the stack lts-9 resolver 2017-09-20 00:19:56 -04:00
stack-8.0.yaml Adds matrix builds for travis 2016-12-09 13:10:19 +01:00
stack.yaml Makes stack.yaml a link again 2017-03-18 20:52:08 +01:00

An API client for docker written in Haskell

Master
master

Current state

Supported Docker Engine Api version: v1.24 and onwards.

Anything upward of that should work since Docker versions their API. Older docker version and engine api versions are not supported at the moment.

Contributing

If you wish to contribute please see any issue tagged with "help wanted". Make sure to submit your PR's against the master 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.

IRC

If you have any questions or suggestions you can find the maintainers in #docker-haskell on freenode.