cloud-setup

Cloud Setup — Transition to Real-Time Sync

Generate the configuration scaffold and architecture guide for organizations that want to move from git-based .omniscitus/ storage to a cloud-backed real-time sync system.

When to Use

• User types /cloud-setup
• User says "클라우드 설정", "omniscitus cloud", "real-time sync"
• Organization needs concurrent editing without git merge conflicts
• Team wants a shared dashboard accessible without localhost

Instructions

Pre-check: Already Configured?

Check if .omniscitus/cloud.yaml exists.

If it exists, read the enabled field and report:

☁️ Cloud config already exists.

  Provider: {backend.provider}
  Enabled: {enabled}
  Sync strategy: {sync.conflict_strategy}

  To modify, edit .omniscitus/cloud.yaml directly.
  To start over, delete .omniscitus/cloud.yaml and run again.

Stop here. Do NOT regenerate.

Step 1: Assess Current State

# Count team members (from blueprint source labels)
grep -r "source: " .omniscitus/blueprints/ 2>/dev/null | sed 's/.*source: //' | sort -u

# Count total tracked files
grep -r "status: active" .omniscitus/blueprints/ 2>/dev/null | wc -l

# Count history units
cat .omniscitus/history/_index.yaml 2>/dev/null | grep "id:" | wc -l

Step 2: Ask Requirements

Use AskUserQuestion:

• "Which cloud provider do you prefer? (AWS, GCP, Azure, or self-hosted)"
• "How many concurrent developers will use omniscitus?"
• "Do you need the shared birdview dashboard accessible from a URL?"

Step 3: Generate Cloud Config

Create .omniscitus/cloud.yaml:

# Omniscitus Cloud Configuration
# Generated by /cloud-setup
# This file configures the cloud sync layer for real-time collaboration.

version: 1
enabled: false  # Set to true when cloud backend is deployed

# Cloud backend connection
backend:
  # Options: "s3", "gcs", "azure-blob", "supabase", "custom"
  provider: "{user_choice}"
  
  # Provider-specific settings (fill in after deployment)
  config:
    # S3 example:
    # bucket: "omniscitus-{project-name}"
    # region: "us-east-1"
    # prefix: ".omniscitus/"
    
    # Supabase example (recommended for small teams):
    # url: "https://xxx.supabase.co"
    # anon_key: "your-anon-key"
    # table_prefix: "omniscitus_"

# Sync behavior
sync:
  # How often to push local changes to cloud (seconds)
  push_interval: 30
  
  # How often to pull remote changes (seconds)
  pull_interval: 15
  
  # Conflict resolution strategy
  # "last-write-wins" — simple, may lose data
  # "merge" — attempts to merge changes (recommended)
  # "manual" — flags conflicts for manual resolution
  conflict_strategy: "merge"
  
  # Which data to sync (all by default)
  include:
    - blueprints
    - history
    - ontology
    - tests
  
  # Exclude patterns
  exclude: []

# Shared dashboard
dashboard:
  # Set to true to deploy birdview as a shared web app
  enabled: false
  # URL will be set after deployment
  url: ""

# Notifications (optional)
notifications:
  # Notify when a team member runs /wrap-up
  on_wrap_up: false
  # Notify on blueprint conflicts
  on_conflict: true
  # Webhook URL (Slack, Discord, etc.)
  webhook_url: ""