2. First deploy

In short. You tell your computer where the server is. You build the app on the server, create the app’s settings file with your login password, and start the app. At the end, the app answers at https://<your-domain> and you can log in. Trading stays off until 4. Go live.

Each command block says where to type it: on the server or on your computer.

Step 1. Fill in your computer’s deploy settings

On your computer, go to the folder of your copy of the repository.
Copy the template of the deploy settings. Git ignores the new file:
cp deploy/deploy.env.example deploy/.deploy.env

Open deploy/.deploy.env in a text editor. Fill in these three lines:

SESAME_DEPLOY_HOST=<your-domain>
SESAME_DEPLOY_KEY=~/.ssh/sesame_deploy
SESAME_ALLOWED_SIGNERS=~/.config/sesame/allowed_signers

Do not change the other lines. Save the file.

Line	What it is
`SESAME_DEPLOY_HOST`	The server. Use the same name as in Step 12 of Prepare the server
`SESAME_DEPLOY_KEY`	The deploy key from Step 7 of Prepare the server
`SESAME_ALLOWED_SIGNERS`	Your list of allowed signers from Step 8 of Prepare the server. Each `task deploy` command checks the tag’s signature against it
`SESAME_DEPLOY_USER`	Keep `deploy`
`SESAME_DEPLOY_PORT`	Keep `22`

Step 2. Build the app on the server

On your computer, in the repository folder, start the deploy:
task deploy -- <tag>
When ssh asks, type the PIN of the security key and touch the key. For a key file, type the passphrase.
Wait. The server gets the tag, checks it and builds the app. The first build takes some minutes.

The command stops with this message:

sesamectl: missing /opt/sesame/sesame.env; create it as root:root 0600 (docs/guides/deploy/2-first-deploy.md)

This result is correct. The app needs its settings file. You create it in Step 3.

Step 3. Create the settings file

On the server, make the hash of your login password:

sudo docker run --rm -it --network none sesame:<tag> hash-password

At Password:, type the password that you will use to log in to the app. The screen does not show it.
Copy the line that the command shows. It starts with $argon2id$ .
On the server, make a random session secret:
openssl rand -hex 32
Copy the line that the command shows. Also keep a copy in your password manager. WARNING: Do not lose the session secret. A backup restores only with the session secret that was set when the app wrote the backup.

On the server, create the settings file and open it:

sudo install -o root -g root -m 0600 /dev/null /opt/sesame/sesame.env
sudoedit /opt/sesame/sesame.env

Write these three lines. Put the hash between single quotes.

UI_PASSWORD_HASH='<the hash from item 3>'
SESSION_SECRET=<the secret from item 5>
LIVE_TRADING=false

Save the file and close the editor.

configuration.md lists the other settings that you can add.

Step 4. Deploy again

On your computer, start the deploy again:
task deploy -- <tag>
Type the PIN and touch the security key, or type the passphrase.

The server uses the build from Step 2 again and starts the app. The command ends with this message:

sesamectl: <tag> is running at https://<your-domain> (previous tag: none)

Is it working?

Check	How	Expected result
The app runs	On your computer: `curl -s https://<your-domain>/api/health`	`{"status":"ok"}`. If you see `degraded`, the location check failed. See Troubleshooting
HTTPS works	Open `http://<your-domain>` in a browser	The address changes to `https://` and the browser shows a padlock
You can log in	Log in with the password from Step 3	The app opens
Polymarket permits the location	Log in, then open `https://<your-domain>/api/status` in the same browser	Under `geoblock`, `"blocked":false`
The correct release runs	On your computer: `task deploy:status`	`SESAME_IMAGE_TAG=<tag>`, and the containers `sesame` and `caddy` are up

On the /api/status page, trading_enabled is false at this time. This is correct. You turn trading on in 4. Go live. If a check fails, see Troubleshooting. Previous: 1. Prepare the server · Next: 3. Backups

Deploy guide

Reference

Runbooks

2. First deploy

2. First deploy

Step 1. Fill in your computer’s deploy settings

Step 2. Build the app on the server

Step 3. Create the settings file

Step 4. Deploy again

Is it working?

​2. First deploy

​Step 1. Fill in your computer’s deploy settings

​Step 2. Build the app on the server

​Step 3. Create the settings file

​Step 4. Deploy again

​Is it working?

2. First deploy

Step 1. Fill in your computer’s deploy settings

Step 2. Build the app on the server

Step 3. Create the settings file

Step 4. Deploy again

Is it working?