Skip to content

Service Startup

Jump to bottom Edit New page
erictj edited this page Jul 6, 2011 · 1 revision

All services within the Locker Project are self-running processes. However, upon starting up, each service needs some information to help it identify itself to the locker instance, as well as to determine the filesystem path of where the service itself resides.

There are three steps regarding starting up a service within a locker:

  1. Manifest: A manifest is a JSON file that contains all information necessary for pre-installation of a service. These manifest files reside within the service, and are copied over to the instance of the service that is instantiated in the locker owner's Me directory.

There are manifests specific to each of the three components of a locker.

  1. me.json: The instance-specific data that's originally pulled from the service manifest file. This file may be refactored for minification based on only necessary data per instance. {id:"...", serviceSource:"connector/facebook"}

  2. stdin: stdin passes in all information regarding how communication occurs between the service and locker core. It will be refactored to only pass in working directory and where to talk to locker core.

Add a custom footer
Add a custom sidebar
Clone this wiki locally