| 1 | zetta-app
|
| 2 | =========
|
| 3 |
|
| 4 | Zetta Toolkit - Application Framework
|
| 5 |
|
| 6 |
|
| 7 | Zetta-App was originally created to help multiple projects stay on top of latest express releases. Zetta-App offers a base application class that contains a number of facilities that may be needed by the application. These facilities can be activated by introducing appropriate configuration file objects.
|
| 8 |
|
| 9 | For example, adding http object to the config file as follows:
|
| 10 |
|
| 11 | ```js
|
| 12 | {
|
| 13 | http : {
|
| 14 | port : 8765
|
| 15 | }
|
| 16 | }
|
| 17 | ```
|
| 18 |
|
| 19 | will automatically instantiate application's http server.
|
| 20 |
|
| 21 | Following features are available:
|
| 22 |
|
| 23 | - Config file loading
|
| 24 | - Event notification during init stages
|
| 25 | - Binding mongodb collections & indexes via config object
|
| 26 | - HTTP server
|
| 27 | - Login subsystem
|
| 28 | - Custom Web Socket interface
|
| 29 | - Translation interface
|
| 30 | - Supervisor connectivity (RPC to a monitoring server)
|
| 31 |
|
| 32 | Application object is reffered to as `core` and contains following:
|
| 33 |
|
| 34 | Application.getConfig()
|
| 35 | Application.readJSON()
|
| 36 | Application.writeJSON()
|
| 37 |
|
| 38 | ### Functions
|
| 39 | - **initBeforeHttp** -
|
| 40 | - **init** -
|
| 41 |
|
| 42 |
|
| 43 | ### Properties
|
| 44 |
|
| 45 | - **uuid** -
|
| 46 | - **config** -
|
| 47 | - **** -
|
| 48 | - **** -
|
| 49 | - **** -
|
| 50 | - **** -
|
| 51 | - **** -
|
| 52 | - **** -
|
| 53 | - **** -
|
| 54 | - **** -
|
| 55 |
|
| 56 | ### Events
|
| 57 |
|
| 58 | - **init::done** -
|
| 59 | - **init::express** -
|
| 60 | - **init::websockets** -
|
| 61 | - **init::http::done** -
|
| 62 | - **init::http-server** -
|
| 63 | - **** -
|
| 64 | - **websocket::connect** -
|
| 65 | - **websocket::disconnect** -
|
| 66 |
|
| 67 |
|