keter/incoming
Christopher Reichert 3ecbe9eb61 Use cabal exec to build incoming examples.
* Don't hardcode sandbox architecture.
2014-12-19 15:41:05 -06:00
..
foo Organize imports in foo1_0/hello.hs and remove unused extension. 2014-12-19 15:17:44 -06:00
foo1_0 Organize imports in foo1_0/hello.hs and remove unused extension. 2014-12-19 15:17:44 -06:00
websockets Add background app configuration example. 2014-12-19 15:10:10 -06:00
Makefile Use cabal exec to build incoming examples. 2014-12-19 15:41:05 -06:00
README.md Add bits of example bundle documentation. 2014-12-19 15:10:10 -06:00

Keter Configuration Examples

Build all examples:

$ make

The resulting build will attempt to use the package-db in the parent directory,

Build Keter app bundle with V1.0 configuration syntax:

$ make foo1_0

Build Keter websocket app bundle:

$ make websockets

Build Keter app bundle with V0.4 configuration syntax:

$ make foo

The resulting bundles are moved into the ./incoming folder and will be unpacked and served by Keter. You can use make clean to clean the incoming directory and remove all bundles.