Recovery workspace

Bring your recipes home.

Keep a recovery copy today. Restore your server and reconnect the latest Recipe Cards data when you need it.

01 · Check & preserve

Your Recipe Cards data

Uses your existing control panel password unless a separate restore password is configured. It is kept only in this page’s memory.

02 · Keep offline

Be ready before an outage

This page runs on the same server as your apps. Download the guide and restore script now so you can use them even when the server is down.

Download guideDownload restore script

Checklist ticks are saved in this browser only. Refresh your snapshot after changing server settings or credentials.

Recipe Cards has no automatic retry for failed Git pushes, and recipe deletions do not trigger a backup. Matching commits alone is not a full backup guarantee.

03 · Recover

Snapshot first. Latest data next.

  1. Create a replacement from your Hetzner snapshot. Use compatible ARM architecture for your CAX11. Keep the old server and prevent edits on both copies.
  2. Sign in with SSH as deploy. Upload the downloaded script to the deploy user’s home folder, then run bash ~/recover.sh. This app may not exist in an older snapshot.
  3. Preserve and compare. The script stops the apps, archives their files privately, and fetches GitHub. It stops if local changes or diverging commits need your attention. It expects origin/main.
  4. Update and restart. When checks pass, it updates the code/data, installs dependencies, reloads settings and starts the apps. If a check fails, resolve it before restarting.
  5. Reconnect and verify. Update DNS and the GitHub deployment IP if needed. Test HTTPS, login emails, latest recipes, photos, cooking history and a new GitHub backup.

Need files from your downloaded bundle instead? The offline guide explains how to extract them into a separate folder and compare them before copying anything into the app.