Move to Chasen

Servers that the older installer set up keep working. Formlander updates itself each night, and the formlander commands stay: formlander update, restore-db, and 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, instead of one a night;
• the chasen commands, also from your computer: status, logs, backups, restore, and rollback.

Move

On the server, as root:

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

1. Install Chasen next to Formlander.
2. Start Chasen. Formlander keeps running.
3. Hand Formlander to Chasen. The container, the data, and the domain stay as they are, and nothing restarts.
4. Remove the nightly update and the command of the older installer.
5. Deploy the newest Formlander through Chasen, with a backup of the database first, and turn on its nightly update.

Your data, your admin password, and your domain stay. These steps run on a fresh server with the older installer on every change to Formlander, 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 formlander status.
• On the server: sudo chasen-server status formlander, and the same for logs and backups.
• Offsite backups: give the server a bucket with chasen bucket. See the Chasen docs.
• Updates: the newest Formlander deploys each night. To update now, run the install line again.
• The backups of the older installer stay where they were.