Deployment & Installation
This guide provides installation and deployment instructions for GLIK Open Core — the self-hosted orchestration runtime designed for enterprise environments requiring local infrastructure control, security customization, or DevOps integration.
GLIK Open Core is distributed as a containerized application, deployable on Linux-based servers, Kubernetes clusters, or virtualized cloud environments. It includes the core orchestration engine, memory runtime, and command-line tooling.
Prerequisites
Before deployment, ensure the following:
System Requirements
OS: Ubuntu 20.04+ or RHEL 8+ (or container-ready equivalent)
CPU: 4-core minimum
Memory: 8 GB RAM minimum (16 GB recommended for high-throughput environments)
Disk: 50 GB+ available storage
Container Runtime: Docker (v20+) or containerd
Network: HTTPS enabled, access to internal plugin endpoints (if applicable)
Access Requirements
SSH access to the target environment
Admin or sudo privileges
Optional: Kubernetes cluster credentials (for K8s deployments)
Installation (Docker Quick Start)
This is the fastest way to get GLIK Open Core running in a dev or staging environment.
git clone https://github.com/rivalz-glik/glik-open-core.git
cd glik-open-core
cp .env.example .env
# Modify configuration in .env (e.g. port bindings, persistence paths)
# Launch with Docker Compose
docker compose up -d
Once running, access the orchestration CLI via:
docker exec -it glik_orchestrator /bin/bash
glik-cli --help
Installation (Kubernetes)
For production or scalable deployments:
# Clone and configure Helm chart
helm repo add glik https://charts.rivalz.ai
helm install glik-core glik/glik-open-core \
--values ./helm/values-prod.yaml
Monitor pods:
kubectl get pods -n glik
Expose ingress endpoints via NGINX, Traefik, or your preferred reverse proxy. Use TLS certificates and API key headers for secured operation.
Post-Install Checklist
Stay Updated
GLIK Open Core is under active development. To monitor updates, feature changes, and new modules:
Visit the official GitHub organization: github.com/rivalz-glik
Check the Repositories tab regularly for newly published components and runtime improvements.
We recommend pulling the latest container images and reviewing release notes before each deployment.
Last updated
Was this helpful?