The OrchestrateDB package

This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.

[maintain]

Warnings:

An implementation of most of the functions of the Orchestrate.io REST API in Haskell. To get started, see the documentation for the Orchestrate and Orchestrate.REST module below. Because this module does use Data.Aeson for parsing and encoding JSON you might want to take a look at it's docs too. For some working examples check out the examples/Test.hs file and the documentation.


[Skip to ReadMe]

Properties

Versions1.0.0.0, 1.0.0.0, 1.0.0.1, 1.0.0.2, 1.0.0.3
Change logNone available
Dependenciesaeson, base (==4.7.*), bytestring (>=0.10), HTTP (>=4000), http-conduit (>=2.1), http-types (>=0.8), lifted-base (>=0.2) [details]
LicenseBSD3
CopyrightCopyright (c) 2015, Adrian Dawid
AuthorAdrian Dawid
Maintaineradriandwd@gmail.com
CategoryDatabase
Home pagehttps://github.com/dwd31415/Haskell-OrchestrateDB
Bug trackerhttps://github.com/dwd31415/Haskell-OrchestrateDB/issues
UploadedTue Jul 28 22:30:59 UTC 2015 by dwd31415

Modules

[Index]

Downloads

Maintainers' corner

For package maintainers and hackage trustees

Readme for OrchestrateDB-1.0.0.0

Haskell-OrchestrateDB Build Status

Unofficial Haskell Client Library for the Orchestrate.io API

How to install this package?

The most convenient way of installing this package is via Hackage, just click on the Hackage badge to get to the project's hackage site. Alternatively, you could also just clone this repository and run the

cabal install

command in it.

Where to find the documentation?

Haddock docs can be found on the hackage project site, but if you want to, you can also build them on your local machine by running

 cabal haddock --html

Tests?

Some tests are run automatically after each commit over the Travis-CI service. If the Travis-CI badge says "build passing" everything should be fine.