Situation #
Pop Dispatch runs well on one computer and you are replacing it with another. You plan the move, so you can choose a quiet hour and lose nothing.
What keeps working #
- The old computer keeps serving until you shut it down, so you can check the new one first.
- Drivers keep working offline and send queued items when a server answers again.
Steps #
- On the old computer, make a backup file now:
POST /backup/archives. The answer showschecked: trueand the file name. - Copy that file from the backup folder to a USB drive. Run
dispatch-server verify-backup <file>and type your recovery key. The command reports the rows and photos inside. This proves the file and the key together. - Install Pop Dispatch on the new computer. Do not create a business account there.
- Choose a quiet time. Stop the old server so nothing changes after the backup. Make one more file after stopping if people worked in between.
- On the new computer, restore the file with the setup wizard (it calls
POST /setup/restore) or rundispatch-server restore <file> --data-dir <data folder>. Type the recovery key. - Run the
reset-passwordcommand it prints for each owner, then for everyone else. - Start the server on the new computer. Set up the authenticator apps again and make new webhook secrets and integration keys.
- Move the old address to the new computer, or tell staff and phones the new address.
- Choose the backup folder on the new computer with
PATCH /backup/settings.
How to confirm it worked #
GET /healthanswersok: trueon the new computer.- The board, the yard and open invoices show what the old computer showed.
- A photo from last week opens.
GET /backup/statusshows a recentlast_goodafter you make a file there.
Afterwards #
- Keep the old computer switched off but untouched for a week. Its data folder is your second copy.
- Erase the old disk after that week and after one good nightly file on the new computer.
- Keep your recovery key unchanged.