| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Since configuration is a nested hash we need to symbolize all keys
of the hash. Othervise fetcing will fail on start
|
|
|
|
|
|
|
|
|
| |
* Service.build takes the literal YAML config hash for the service and a
reference to the Configurator that's doing the building.
* Services that compose additional services can use the Configurator to
look them up and build them by name. See MirrorService for an example.
References #23
|
|
* Move service configuration from the Engine to Service
* Delegate configuration mechanics to internal Service::Configurator
* Delegate service building to the concrete Service classes, allowing
them to configure composed services.
* Implement for the Mirror service.
|