> ## Documentation Index > Fetch the complete documentation index at: https://docs.sesameterminal.com/llms.txt > Use this file to discover all available pages before exploring further. # Day to day # Day to day > **In short.** After the setup, you run the app with one `task deploy:...` command for each > job: install a release, go back to the previous one, read the logs, change a setting, back > up and restore. This page also turns on Telegram notifications. Look up the job you need. ## Before you run a command * Type each `task deploy:...` command on **your computer**, in the repository folder, in the terminal. On Windows, use Git Bash. * Each command asks for the security key's PIN and a touch, or for the key's passphrase. * The server runs one command at a time. A second command while one runs stops with `sesamectl: another sesamectl run is in progress`. Wait, then try again. * The commands use the newest `release-*` tag on your computer. If you work in a new copy of the repository, get the tags first: ```sh theme={null} git fetch origin 'refs/tags/release-*:refs/tags/release-*' ``` ## Commands | To | Run on your computer | | - | - | | [Install a new release](#install-a-new-release) | `task deploy -- ` | | [Go back to the previous release](#go-back-to-the-previous-release) | `task deploy:rollback` | | [See which release runs](#see-which-release-runs) | `task deploy:status` | | [Read the app's last 300 log lines](#read-the-logs) | `task deploy:logs -- sesame` | | [Read the web server's last 300 log lines](#read-the-logs) | `task deploy:logs -- caddy` | | [Apply a change to `sesame.env`](#change-a-setting) | `task deploy:start` | | [Turn trading off](#turn-trading-off) | `LIVE_TRADING=false` in `sesame.env`, then `task deploy:start` | | [Back up now](#back-up-now) | `task deploy:backup-now` | | [List the backups on the server](#restore-a-backup) | `task deploy:list-backups` | | [Restore a backup](#restore-a-backup) | `task deploy:restore -- ` | | Start the app after a failed restore | `task deploy:start` | ## Install a new release 1. Sign and push a new release tag, as in [Prepare the server, step 8, item 3](1-prepare-server.md#step-8-set-up-release-signing-and-sign-the-first-release). 2. On **your computer**, install it: ```sh theme={null} task deploy -- ``` The server checks the tag's signature and builds the app. If the app runs, the server then backs up the database, before it starts the new release. You can then go back to the data from before the update. The command ends with: ```text theme={null} sesamectl: is running at https:// (previous tag: ) ``` If the command also prints `deploy/sesamectl in differs from /usr/local/sbin/sesamectl`, follow [Updating the server scripts](advanced.md#updating-the-server-scripts). ## Go back to the previous release On **your computer**: ```sh theme={null} task deploy:rollback ``` It prints `sesamectl: rolling back from to `. The command swaps the current release and the previous release. Run it a second time to return to the newer release. To go back to an older release that is still on the server, name its tag: ```sh theme={null} task deploy:rollback -- ``` A rollback does not change the data. If the newer release changed the database, the older release does not start. Its log then shows `is newer than the` and a number of `known migrations`. In that case, restore the backup that the update took ([Restore a backup](#restore-a-backup)). Changes made after the update are lost. ## See which release runs On **your computer**: ```sh theme={null} task deploy:status ``` It shows `SESAME_IMAGE_TAG=` (the release that runs), `SESAME_PREVIOUS_IMAGE_TAG=` (the release a rollback goes to) and the state of the two containers. ## Read the logs On **your computer**, read the app's last 300 log lines: ```sh theme={null} task deploy:logs -- sesame ``` Read the web server's last 300 log lines: ```sh theme={null} task deploy:logs -- caddy ``` For more than 300 lines, run this on **the server**: ```sh theme={null} cd /opt/sesame && sudo docker compose logs sesame ``` ## Change a setting 1. On **the server**, open the settings file: ```sh theme={null} sudoedit /opt/sesame/sesame.env ``` 2. Change the line, then save and close the file. Each setting is explained in [configuration.md](../configuration.md). 3. On **your computer**, restart the app with the new values: ```sh theme={null} task deploy:start ``` The command ends with a list of the two containers. If it stops with an error, see [The deploy stops and the app does not start](troubleshooting.md#the-deploy-stops-and-the-app-does-not-start). ## Turn trading off Do this to stop all real orders at once, for example when something looks wrong. 1. In the app, press **Cancel all**. 2. On **the server**, open the settings file: ```sh theme={null} sudoedit /opt/sesame/sesame.env ``` 3. Change the `LIVE_TRADING` line to: ```dotenv theme={null} LIVE_TRADING=false ``` 4. On **your computer**, restart the app: ```sh theme={null} task deploy:start ``` The app then shows **Trading off**. To turn trading on again, set `LIVE_TRADING=true` and run `task deploy:start`. If a key may be exposed, follow the [incident runbook](../../runbooks/incident.md) as well. ## Back up now On **your computer**: ```sh theme={null} task deploy:backup-now ``` It prints the name of the new backup, for example `sesame-20261001T040000Z.db`. It also encrypts the backup for the backup machine. ## Restore a backup A restore replaces the app's data with a backup. The app stops while the restore runs. CAUTION: Cancel your open orders first if they matter. The app cannot act on them while it is stopped. 1. On **your computer**, take a backup, so you can undo the restore: ```sh theme={null} task deploy:backup-now ``` 2. List the backups on the server: ```sh theme={null} task deploy:list-backups ``` Each backup is a `sesame-