Move to new hardware
You will carry an atfs instance's identity onto a different board.
This page only applies when you deploy to an SD-card device.
Moving an atfs instance to new hardware means moving its libp2p identity
key, not its data. The instance’s dev.atfs.server record names a peer ID,
and that peer ID is derived from the identity key. Keep the same key, and
the same record keeps working.
- Read the old device’s
ATFS_IDENTITY_KEYvalue. If it was never set explicitly, copy the raw key file from the old device’s data directory instead. - Set that same value on the new device, either with the setup tool or by editing settings by hand.
- Flash the new device.
- Boot the new device.
- Confirm the new device is healthy. See Is it healthy?.
- Point your DNS record at the new device. Use the domain your
serviceDidnames. - Power off the old device for good.
Warning
Never boot two devices with the same identity key at the same time. One dev.atfs.server record names one peer. Retire the old card fully before
the new one goes live.
Moving the files already stored on the old device is a manual copy today — there is no built-in migration tool yet.
For how settings and the identity key are kept safe across an ordinary reflash, see Why credentials survive a reflash.