spatial-connect | Responsible for scheduling containers

Clone the repositories mentioned above (Spatial Connect, Spatial Connect CLI, GeoServices)
Build all of the libraries from source
Open Spatial Connect and ensure that all library references are ok, include/update anything that is missing or broken During this step you will need to update the references for several ESRI.* libraries. These are installed with the ArcObjects SDK and can typically be found at this path on Windows C:\Program Files (x86)\ArcGIS\DeveloperKit10.4\DotNet\
Use Spatial Connect CLI to initialize a connect space and create a container
Rename the Example-App.config in the Spatial.Connect.Task project to App.config and populate the following: app.settings > app-path : this should be the direct path to the directory created in step 4. system.servicemodel > client > endpoint : replace the address attribute with the address of your instance of WebEOC API
Create two Windows Scheduled Tasks, one for push and one for pull. Push and Pull tasks should reference the executable built from the Spatial.Connect.Task project. Additionally they should supply either 'push' or 'pull' as an input argument to indicate their purpose to the executable.
Run the schedule tasks. Notifications of service actions will be logged to log.txt inside the /log folder found inside the directory created in step 4.