systemg

A general-purpose program orchestrator.

Table of Contents

1. Read the Docs
2. Getting Started
   • 2.1 Installation
   • 2.2 Usage
3. Why systemg
   • 3.1 Features
4. How systemg Compares

Getting Started

Installation

$ curl --proto '=https' --tlsv1.2 -fsSL https://sh.sysg.dev/ | sh

System deployments: scripts/install-systemg.sh sets up /usr/bin/sysg, /etc/systemg, /var/lib/systemg. See security guide.

Usage

Tip: --stderr redirects stderr from supervised processes to stdout with a [service_name:stderr] prefix, which is useful for debugging and CI pipelines.

By default, systemg captures service stdout/stderr through pipes and persists a local copy under its log directory. For high-output services, configure logging explicitly:

logs:
  sink: file
  max_bytes: 10485760
  max_files: 5
status:
  snapshot_mode: summary
  snapshot_interval_secs: 5
services:
  noisy_worker:
    command: "worker --verbose"
    logs:
      sink: none

sink: none discards service output without creating systemg log-writer threads or files, which is useful when another production logging pipeline already collects process output.

status.snapshot_mode: summary keeps sysg status and sysg inspect inexpensive while still reading current persisted state such as cron history. Use detailed only when you need process tree and runtime command details for diagnostics. Add --live to sysg status or sysg inspect when a single request should force immediate runtime collection instead of the configured snapshot mode.

Why systemg

Compose programs into systems with explicit dependencies and health checks.

Features

• Dependencies - Topological startup order with health-aware cascading
• Rolling Deployments - Blue-green swaps with health validation
• Environment - .env file propagation
• Webhooks - Event notifications (docs)
• Cron - Scheduled tasks with overlap detection
• Spawning - Dynamic child process tracking
• OS Integration - systemd/cgroups when available
• Single Binary - No runtime dependencies

How systemg Compares