Skip to content

Move deployment to new server and SQLite volume - #103

Merged
kcdragon merged 1 commit into
mainfrom
move-app-sqlite-to-server
Aug 1, 2026
Merged

Move deployment to new server and SQLite volume#103
kcdragon merged 1 commit into
mainfrom
move-app-sqlite-to-server

Conversation

@kcdragon

@kcdragon kcdragon commented Aug 1, 2026

Copy link
Copy Markdown
Collaborator

Points the Kamal deployment at the new Hetzner server (178.156.170.199) and the new block volume (ID 106515620) that persists the SQLite databases and local Active Storage files at /rails/storage. Only config/deploy.yml changes — registry, secrets, Dockerfile, and the rowhomelabs.com proxy hosts are untouched.

Cutover requires copying the existing volume data (all four production SQLite DBs plus Active Storage uploads) from the old volume to the new one and chowning it to uid/gid 1000 before kamal setup; DNS repoint and old-server decommission are handled separately.

🤖 Generated with Claude Code

Point Kamal at the new Hetzner server (178.156.170.199) and the new block
volume (ID 106515620) that persists the SQLite databases and local Active
Storage files at /rails/storage.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@kcdragon
kcdragon merged commit 1a52f12 into main Aug 1, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant