Move to Chasen

Servers that the older installer set up keep working. LogNorth updates itself each night, and the lognorth commands stay: lognorth update, status, and reset-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.

Move

On the server, as root:

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

1. Install Chasen next to LogNorth.
2. Start Chasen. LogNorth keeps running.
3. Hand LogNorth 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 LogNorth through Chasen, with a backup of the database first, and turn on its nightly update.

Your data, your account, your private key, and your domain stay, so nobody is signed out. These steps run on a fresh server with the older installer before each release of LogNorth, 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 lognorth status.
• On the server: sudo chasen-server status lognorth, and the same for logs and backups.
• Offsite backups: give the server a bucket with chasen bucket. See the Chasen docs.
• Updates: the newest LogNorth deploys each night. To update now, run the install line again.
• A forgotten password: chasen -a lognorth ssh, then /app/lnctl reset-password you@example.com.