kenpat/kitestacks-homelab
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
kitestacks-homelab/cloud-migration/README.md
kenpat fb822d5142 Reorganize repos into kitestacks-homelab + plain-English doc rewrite 
- Rewrote RUNBOOK.md and DEBUG-DOCUMENTATION.md in simple 5th-grade language
  with real-world analogies for every technical concept
- Updated README.md with current service inventory and folder map
- Added cloud-migration/ subdirectory (from kitestacks-cloud-migration repo)
- Added autosync/ subdirectory (from kitestacks-homelab-autosync-test repo)
- Added osticket/ subdirectory (from OSTicketSystem repo)
- Added cloud/ placeholder for future cloud configs
- Excluded binary DB/postgres files from autosync subdirectory

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-18 18:37:58 -05:00

2.1 KiB
Raw Blame History

KiteStacks Cloud Migration Backup

Created for migrating the current KiteStacks host to Hetzner Cloud.

Contents

  • archives/docker-bind-data.tar.gz - /home/kenpat/docker bind-mounted service folders, including compose files, .env files, and bind-mounted app data.
  • archives/syncthing-shared.tar.gz - /home/kenpat/SyncthingShared.
  • archives/kitestacks-scripts.tar.gz - local KiteStacks automation/script folders.
  • archives/host-etc-subset.tar.gz - selected host /etc configuration needed for migration context.
  • volume-exports/*.tar.gz - Docker named volume exports.
  • inventory/* - Docker, network, disk, config, and host inventory.
  • restore/RESTORE.md - first-pass restore procedure.
  • SHA256SUMS - checksums for all files in this backup.

Restoring Claude's Context on a New Machine

This repo includes a snapshot of Claude Code's persistent memory in claude-memory/ (taken from ~/.claude/projects/-home-kenpat/memory/ on the original host). It captures the homelab setup, this migration plan/status, and your working preferences, so a fresh Claude session on the new machine doesn't start blank.

To restore it:

  1. Clone this repo on the new machine.
  2. Copy the contents of claude-memory/ into Claude Code's memory directory for your new home path, e.g.: 
    mkdir -p ~/.claude/projects/-home-<youruser>/memory
cp claude-memory/*.md ~/.claude/projects/-home-<youruser>/memory/
  3. Start a Claude Code session in that project. It will automatically load MEMORY.md and the linked memory files, and can pick up the migration (and any other tracked work) where it left off.
  4. Update claude-memory/project-cloud-migration.md as migration phases progress, and re-copy it back into this repo so future restores stay current.

Important

This repository contains secrets: .env files, tunnel tokens, app database data, and service credentials. Keep it private.

The Docker bind-data archive was created from a live host. For databases with strict consistency requirements, prefer restoring service-native dumps when available, or stop services before taking a final cutover backup.