# KGrid Activator
# Quick Start
This Quick Start Guide (opens new window) provides the instruction for downloading, configuring and running the KGrid Activator as a Spring-Boot application.
Additional information can be found for:
# Deploy a cloud native image
KGrid Activator can also be deployed using the cloud native image, published at DockerHub. Instructions can be found at Containerization Documentation (opens new window)
A cloud native image of the activator can also be built from the source code. Please refer to the section of Build Image (opens new window) in the above page.
# Running With External Runtime
The activator also has a proxy adapter which can connect to an external runtime and execute code natively in that environment.
Currently we have created two reference implementations:
- KGrid Python Runtime (opens new window), a PyPi package, which can be used to execute Python code. The project can be found in this GitHub repo (opens new window)
The external runtimes can also be deployed using the container images. Please refer to the Cloud native section in the above documentation for each respective runtime.
# Security Configuration
Security Configuration can be set as environment variables, or passed into the terminal command while running the activator. Details can be found in the Configuration Documentation (opens new window)
# Loading KOs into the activator
A Knowledge Object (KO) or a collection of KOs can be loaded into the activator in a number of ways.
- On startup, KOs can be loaded directly from the shelf, as described in the Quick Start Guide (opens new window)
The shelf location can be specified using the shelf location configuration (opens new window).
On startup, KOs can also be loaded with the specified manifest(s). Please refer to the Configuration Documentation, see kgrid-shelf-manifest (opens new window)
Once the activator is running, the KOs can be loaded via the API by posting one of the three endpoints:
/kos/manifest-list. For usage, please refer to Import API (opens new window)
After successfully loading the KOs to the activator via the API,
/reload is needed to activated the newly added KOs. (See Activation API - Reload (opens new window) )