Move to Chasen

Servers that the older installer set up keep working. Fusionaly updates itself each night, and the fusionaly commands stay: fusionaly update, change-admin-password.

Move to Chasen for:

• a live copy of each change in your own S3 bucket, about a second behind, and a checked snapshot every hour;
• the chasen commands, also from your computer: status, logs, backups, restore, and rollback.

A server that still runs Fusionaly Pro switches to the free Fusionaly first, with its data:

curl -fsSL https://fusionaly.com/install | sudo bash -s migrate-to-oss

Move

On the server, as root:

fusionaly update
curl -fsSL https://chasenhq.com/server | sh
chasen-server setup
chasen-server adopt fusionaly
rm /etc/cron.d/fusionaly-update /usr/local/bin/fusionaly
curl -fsSL https://fusionaly.com/install | sudo bash

1. Update Fusionaly first. An older server may still run Caddy; the update moves it to the proxy that Chasen shares.
2. Install Chasen next to Fusionaly.
3. Start Chasen. Fusionaly keeps running.
4. Hand Fusionaly to Chasen. The container, the data, and the domain stay as they are, and nothing restarts.
5. Remove the nightly update and the command of the older installer.
6. Deploy the newest Fusionaly through Chasen, with a backup of the database first, and turn on its nightly update.

Your data, your account, and your domain stay. These steps run on a fresh server with the older installer before each release of Fusionaly, to check exactly that.

After the move

• From your computer: install the CLI with curl -fsSL https://chasenhq.com/cli | sh, log in with chasen add server root@<your server>, then chasen -a fusionaly status.
• On the server: sudo chasen-server status fusionaly, and the same for logs and backups.
• Offsite backups: give the server a bucket with chasen bucket. See the Chasen docs.
• Updates: the newest Fusionaly deploys each night. To update now, run the install line again.
• A forgotten password: chasen -a fusionaly ssh, then /app/fnctl change-admin-password you@example.com.