Dossier 1.1.0

Dossier 1.1.0

Your sign-in password is no longer kept in plain text. DOSSIER_PASSWORD now holds a hash of it, so reading the server's environment doesn't reveal it. This release needs one change to your configuration before it starts: see Upgrading below.

What's new

• Password hash: DOSSIER_PASSWORD takes an argon2id hash of your password instead of the password itself. Make one with docker run --rm -it ghcr.io/aientech/dossier hash-password: it asks for the password twice without showing it and prints the line to paste. The server doesn't start while DOSSIER_PASSWORD is the password itself, and its log says how to make the hash.
• Forgot your password? The sign-in page now says what to do: make a hash of a new one with hash-password, set it and restart.

Upgrading

Take a backup first (see Upgrading in the README). Then:

1. Make the hash with the new image: docker run --rm -it ghcr.io/aientech/dossier:v1.1.0 hash-password. Type your current password to keep it.
2. CapRover: set DOSSIER_PASSWORD to the hash in App Configs, save, and deploy ghcr.io/aientech/dossier:v1.1.0 straight away: until then, 1.0 takes the hash itself as the password. Compose: put the hash in .env, then docker compose -f compose.production.yml pull && docker compose -f compose.production.yml up -d.

Every browser is signed out once and signs in again with the same password. If the new version doesn't start and its log says "DOSSIER_PASSWORD must be a hash of your password", the variable still holds the password itself.