ilyakooo0/docker-hs
1
0
Fork 0
mirror of https://github.com/ilyakooo0/docker-hs.git synced 2024-09-11 10:35:29 +03:00
Code Issues Projects Releases Wiki Activity
A Haskell library for the Docker Engine API
204 Commits 5 Branches 14 Tags 446 KiB
Haskell 98.4%
Makefile 1%
Shell 0.6%
6dbf176f5b
Go to file
Deni Bertovic 6dbf176f5b Updates docs and examples
2017-03-20 11:05:11 +01: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 Updates docs and examples 2017-03-20 11:05:11 +01:00
tests fix tests for streaming 2017-03-09 21:35:11 -05:00
.gitignore Ignores dist-newstyle dir 2016-09-07 16:45:05 +02:00
.travis.yml Travis: Only build master branch and release tags 2017-03-18 20:59:30 +01:00
CHANGELOG.md Adds changelog 2016-09-07 16:47:29 +02:00
CONTRIBUTING.md Adds placeholder for contrib doc 2016-09-05 15:49:20 +02:00
docker.cabal work on switching API to conduit. Still more to do and lots to clean up 2017-02-10 03:15:26 -05:00
LICENSE Bumps LICENSE year 2016-08-10 12:32:17 +02:00
Makefile Small makefile change 2016-09-05 15:48:56 +02:00
README.md Adds note about docker engine api support 2017-03-18 22:04:05 +01:00
Setup.hs initial commit 2014-09-19 19:52:30 +02:00
stack-7.10.yaml Makes stack.yaml a link again 2017-03-18 20:52:08 +01: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

README.md

An API client for docker written in Haskell

Master
master

Current state

API is still not stable.

Supported Docker Engine Api version: v1.24

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.