Hackage :: [Package]

mellon-web: A REST web service for Mellon controllers

[ bsd3, library, web ] [ Propose Tags ] [ Report a vulnerability ]

The mellon-web package wraps a mellon-core controller in a REST web service, making it possible to control physical access devices from an HTTP client. The package includes both a WAI application server, and native Haskell client bindings for the service.

Like the mellon-core controller interface, the mellon-web REST API is quite simple. There are only 3 methods:

  • GET /time returns the system time on the server. This is made available for diagnostic purposes, primarily to ensure the server has an accurate clock.

  • GET /state returns the controller's current state (either Locked or Unlocked date where date is the UTC time at which the controller will automatically lock again).

  • PUT /state sets the controller's current state. Use this method to lock and unlock the controller.

See the included API.md document for detailed documentation on the REST service.

Note that the mellon-web server does not provide an authentication mechanism! You should proxy it behind a secure, authenticating HTTPS server such as Nginx.

[Skip to Readme]

Modules

[Last Documentation]

  • Mellon
    • Web
      • Mellon.Web.Client
      • Mellon.Web.Server
        • Mellon.Web.Server.API
        • Mellon.Web.Server.DocsAPI

Flags

Manual Flags

NameDescriptionDefault
test-hlintEnabled
mock-exampleEnabled
gpio-exampleEnabled
client-unlock-exampleEnabled

Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

Versions [RSS] 0.7.0.1, 0.7.0.3, 0.7.1.0, 0.7.1.1, 0.8.0.2, 0.8.0.3, 0.8.0.4, 0.8.0.5, 0.8.0.6, 0.8.0.7
Change log changelog.md
Dependencies aeson (>=0.11 && <0.12), base (>=4.8 && <5), bytestring (>=0.10 && <0.11), exceptions (>=0.8.0 && <1), hpio (>=0.8 && <1), http-client (>=0.4 && <0.5), http-client-tls, http-types (>=0.9 && <0.10), lucid (>=2.9 && <2.10), mellon-core (>=0.7 && <0.8), mellon-gpio (>=0.7 && <0.8), mellon-web, mtl, network (>=2.6 && <2.7), optparse-applicative (>=0.11.0 && <0.13), servant (>=0.7.1 && <0.10), servant-client (>=0.7.1 && <0.10), servant-docs (>=0.7.1 && <0.10), servant-lucid (>=0.7.1 && <0.10), servant-server (>=0.7.1 && <0.10), text (>=1.2 && <1.3), time (>=1.5 && <2), transformers (>=0.4.2 && <0.6), wai (>=3.2 && <3.3), warp (>=3.2 && <3.3) [details]
Tested with ghc ==7.10.3, ghc ==8.0.1
License BSD-3-Clause
Copyright Copyright (c) 2016, Drew Hess
Author Drew Hess <src@drewhess.com>
Maintainer Drew Hess <src@drewhess.com>
Category Web
Home page https://github.com/dhess/mellon/
Bug tracker https://github.com/dhess/mellon/issues/
Source repo head: git clone git://github.com/dhess/mellon.git
this: git clone git://github.com/dhess/mellon.git(tag v0.7.0.3)
Uploaded by dhess at 2016-09-24T00:27:26Z
Distributions
Executables mellon-schedule-unlock, gpio-mellon-server, mock-mellon-server
Downloads 5710 total (18 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs not available [build log]
All reported builds failed as of 2016-11-19 [all 2 reports]

Readme for mellon-web-0.7.0.3

[back to package description]

mellon-web

The mellon-web package wraps a mellon-core controller in a REST web service, making it possible to control physical access devices from an HTTP client. The package includes both a WAI application server, and native Haskell client bindings for the service.

Like the mellon-core controller interface, the mellon-web REST API is quite simple. There are only 3 methods:

  • GET /time returns the system time on the server. This is made available for diagnostic purposes, primarily to ensure the server has an accurate clock.

  • GET /state returns the controller's current state (either Locked or Unlocked date where date is the UTC time at which the controller will automatically lock again).

  • PUT /state sets the controller's current state. Use this method to lock and unlock the controller.

See API.md for detailed documentation on the REST service.

Note that the mellon-web server does not provide an authentication mechanism! You should proxy it behind a secure, authenticating HTTPS server such as Nginx.

Example servers

"Mock" server

An extremely simple example server (with on-line documentation support) is provided in the examples directory. You can run it with cabal run mock-mellon-server and test it using the endpoints described in API.md. The server is will run on the localhost loopback interface on port 8081.

Also included is a Paw file with a pre-defined localhost environment for use with the example server.

This particular example server uses a "mock lock" device which only internally logs lock and unlock events without depending on any actual hardware, so it will run anywhere.

GPIO server

Another included example server uses the mellon-gpio package to drive a simple physical access device via a GPIO pin. This server must be run on a Linux host with GPIO hardware, e.g., a Raspberry Pi running Linux.

This server takes a GPIO pin number and a local port number, then starts a mellon-web server on all local interfaces on the specified port. When the server receives an unlock request, it will drive a high signal on the specified GPIO pin. When the unlock expires, or when the server receives a lock request, it will drive a low signal on the specified GPIO pin.

To use this server, simply connect a properly-designed physical access device (e.g., an electric strike driven by a relay circuit such as the one shown here) to an available GPIO pin on the host device, then run the server with the specified GPIO pin number and port. For example, to run the server on port 7533 using GPIO pin 65:

cabal run gpio-mellon-server -- sysfs --port 7533 65

The sysfs command tells the server to use the Linux sysfs GPIO interpreter. (Currently, this is the only supported GPIO platform.)

NOTE: the REST service provided by gpio-mellon-server offers no security/authentication for your access control device! You should always run it (or any mellon-web server) behind a secure proxy web service or equivalent HTTP(S)-based authentication mechanism.

Travis CI build status