Fly.io (unsupported archive)
Fased does not currently support running the full Gateway on Fly.io. The files
under deploy/hosting/fly*.toml are retained as historical reference and are
not a maintained, release-tested installation path.
Do not use the archived Fly manifests for a new deployment. They do not provide
the root-managed native signer/updater, separate signer application and control
sockets, Tailscale-first host hardening, coordinated rollback, or cold-reboot
validation required by the supported Hosting profile. Wallet, Vault, and SAT
mining must not be enabled on this path.
Supported alternatives
There is no install.sh --hosting-docker mode. A private Fly proxy or volume
does not make the archived deployment equivalent to the Hosting security and
update lifecycle.
Migrating an existing Fly deployment
- Stop changes to the existing deployment.
- Export the configured Fased state directory and every Agent workspace.
- Treat the export as sensitive because it can contain provider, channel, and
session credentials. Do not copy signer or wallet material through an
unreviewed migration script.
- Install Fased on a clean VPS with
install.sh --hosting.
- Restore only reviewed, compatible non-custody configuration and workspace
data, then re-enroll wallet custody through the native signer workflow.
- Verify
fased health, Gateway status, plugins, signer health, and each
channel before deleting the old Fly volume or secrets.
Use the provider console to remove the legacy app, public IPs, volumes, and
secrets only after the new VPS is verified and backed up.