OrchestrateDB: Unofficial Haskell Client Library for the Orchestrate.io API

[ bsd3, database, library ] [ Propose Tags ]

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]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

Versions [RSS] 1.0.0.0, 1.0.0.1, 1.0.0.2, 1.0.0.3
Dependencies aeson, base (>=4.7 && <4.9), bytestring (>=0.10), HTTP (>=4000), http-conduit (>=2.1), http-types (>=0.8), lifted-base (>=0.2) [details]
License BSD-3-Clause
Copyright Copyright (c) 2015, Adrian Dawid
Author Adrian Dawid
Maintainer adriandwd@gmail.com
Category Database
Home page https://github.com/dwd31415/Haskell-OrchestrateDB
Bug tracker https://github.com/dwd31415/Haskell-OrchestrateDB/issues
Uploaded by dwd31415 at 2015-07-29T11:44:31Z
Distributions
Reverse Dependencies 1 direct, 0 indirect [details]
Downloads 2980 total (12 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2015-07-29 [all 1 reports]

Readme for OrchestrateDB-1.0.0.1

[back to package description]

Haskell-OrchestrateDB

Build Status Hackage GitHub license Hackage-Deps

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.