LogoLogo
Home
Installation
Installation
  • Introduction
  • Deployment Alternatives
    • Kubernetes Deployment
      • Prerequisites
      • Recommended: Helm - Fully Automated
      • Alternative 1: Ansible - Fully Automated
      • Alternative 2: Ansible - Step-by-Step
      • Cloud Specific Details
    • Sandbox VM Deployment
      • AWS AMI - Developer Lite
    • Local Test Deployment
  • Artifacts
    • Helm Charts
      • Umbrella Charts
        • Ready Core
        • Ready CMS
        • Ready PIM
      • Initialization Charts
        • Namespaces
        • Global
        • Loader
        • Deployer API
        • Deployer
      • Application Charts
        • Admin UI
        • Gateway
        • Spring Runner
        • Samza Runner
        • Socket Runner
        • Storefront
      • Batch Charts
        • Cron
        • Job
      • Deprecated
        • Authentication
        • Session
        • H2O Wave
        • Wave App
    • Deployment Assets
      • Deprecated
    • Docker Repository
      • Front-end Images
      • Back-end Images
      • Python Images
    • Maven Repository
      • Core Packages
      • Runner Packages
      • Processors Packages
      • Custom Packages
      • Gateway Packages
    • Python Packages
    • Terraform Configurations
    • Ansible Playbooks
      • Initialization Playbooks
      • Application Playbooks
      • Enabler Playbooks
  • Administration
    • Cost & License Management
    • Secrets & Config Management
    • Testing & Health-Check
    • Logs & Traces & Metrics
    • Backup & Recovery
    • Technical Support
Powered by GitBook

© Rierino Software Inc. 2025. All rights reserved.

On this page
  • Configuration
  • Launch
  1. Deployment Alternatives

Sandbox VM Deployment

For testing and development purposes a single VM sandbox is also available.

Sandbox environment provides a quick deployment option for testing and basic development activities, using Docker compose approach. This environment requires a single VM with the following minimum requirements:

  • 4 vCPU

  • 16 GB RAM

This deployment includes the following components which can be disabled using different profiles and services in docker compose commands:

  • Admin UI

  • Admin Controller

  • Admin Runner (with Core platform services as well as optional PIM, CMS, training modules)

  • Ops Runner (used with optional modules for CDC and real-time data synch)

  • MongoDB

  • Kafka

  • Elasticsearch

Configuration

Following environment variables have to be configured in "composite/.env" file before deployment:

  • RIERINO_VERSION: Rierino version to be deployed

  • GITHUB_USER: Provided username for access to Rierino assets

  • GITHUB_AUTH_TOKEN: Provided authentication token for access to Rierino assets

  • PUBLIC_ADDRESS: Public domain name or IP address of the VM (optional, used for client side API calls)

As an option, OpenAI related environment variables can be configured in "composite/adminui.env" file for enabling AI assitant use in admin UI.

Launch

Once the environment files are set, "compose/compose.yaml" file can be used to launch the services.

PreviousCloud Specific DetailsNextAWS AMI - Developer Lite

Last updated 4 months ago

The sandbox assets can be found at the with "composite/README.MD" file for more details on launch and administration commands.

sandbox repository