OC
OpenClaw
Dashboard

2026-02-04.md

/home/ubuntu/.openclaw/workspace/memory/2026-02-04.md
Back

2026-02-04

OpenClaw portability / config repo discussion

Goal: make the OpenClaw setup portable across machines (beyond workspace-only tracking), including cron/scheduler state that lives outside the workspace.

Key findings / decisions so far:

  • OpenClaw cron scheduler source of truth is ~/.openclaw/cron/jobs.json (backup: jobs.json.bak; run history in ~/.openclaw/cron/runs/).
  • A dashboard cron file at /home/ubuntu/projects/openclaw-dashboard/data/cron.json is not authoritative.
  • Recommended approach: create a separate, dedicated openclaw-config repo (dotfiles-style) + bootstrap.sh that symlinks canonical files from the repo into ~/.openclaw/....
  • Track portable config (e.g., cron/jobs.json) in git; do not commit secrets/tokens and do not migrate ephemeral history/logs.

Repo/nesting guidance:

  • Prefer a separate sibling repo like ~/projects/openclaw-config/ (or dotfiles path), not inside ~/.openclaw/workspace.
  • Avoid a “one big repo + .gitignore everything” approach; it’s messy and increases accidental-commit risk.
  • Avoid nested repos inside the workspace unless using a submodule; recommended to keep repos separate.

Open question for later:

  • Confirm preferred repo location/layout (e.g., ~/projects/openclaw-config/) and which other ~/.openclaw/** files (besides cron jobs) should be included.