Skip to content

v1.3.3 - Empty installs, safe demo seed

Latest

Choose a tag to compare

@simonro simonro released this 18 Sep 16:50
· 4 commits to main since this release

Every install starts empty, and the demo seed can no longer overwrite your journal.

Not financial advice. Not a signal service. Every screenshot is the synthetic demo seed.

A new install has no data

A new install, whether from the ZIP, a git clone or setup.bat, starts with no accounts, no trades and no demo data. Setup and the README no longer suggest loading the demo data. Add an account, then import your broker's statement.

Fixed: the demo seed could delete your database

scripts/seed_demo.py builds the synthetic data used for the screenshots. It deleted any existing backend/trading_journal.db without asking, so running it after importing real trades would have wiped them. It now refuses when a database exists and changes nothing, unless you pass --replace-database. It is documented as a development tool only.

Also

  • Questions now go to Discussions; Issues are for bugs, feature requests and broker importer requests.
  • main is protected: a pull request merges only when the backend tests and the frontend build pass. Dependabot alerts and security updates are on.

Install

Download the zip below, unzip it, run setup.bat, then launch.bat. Python 3.11 or newer and Node 18 or newer.

Upgrading

Your trades (backend/trading_journal.db) and your keys (backend/.env) are not part of a release, so updating never touches them.

If you cloned with git: git pull, then launch.bat.

If you downloaded the ZIP: unzip this one into a new folder, copy your two files across, run setup.bat once, then start it with launch.bat.

old-folder/backend/.env                 ->  new-folder/backend/.env
old-folder/backend/trading_journal.db   ->  new-folder/backend/trading_journal.db