7 Commits

Author SHA1 Message Date
f211e422b0 Merge pull request #19 into master
67d27f0 markdown: bump docker-finance to v1.4.1 (Aaron Fiore)
2026-03-18 12:28:22 -07:00
67d27f0c96 markdown: bump docker-finance to v1.4.1 2026-03-18 12:16:36 -07:00
2460fa3e00 Merge pull request #18 into master
1c73977 markdown: add "Ledger Live" account name(s) caveat (Aaron Fiore)
2026-03-18 12:15:18 -07:00
1c7397708c markdown: add "Ledger Live" account name(s) caveat 2026-03-18 11:52:46 -07:00
058a5ab81d Merge pull request #17 into master
8ab18d8 markdown: bump docker-finance to v1.4.0 (Aaron Fiore)
2026-03-16 13:47:59 -07:00
8ab18d8d0c markdown: bump docker-finance to v1.4.0 2026-03-16 12:54:25 -07:00
41566ed81f Merge pull request #16 into master
e9363bd markdown: minor tweak of intro scope (Aaron Fiore)
2026-03-09 13:53:57 -07:00
2 changed files with 9 additions and 1 deletions

View File

@@ -64,7 +64,7 @@ To get started, you'll only need a modern Linux client (host) with a working Doc
```bash
# NOTE: you can change the domain to `gitea.com`, as this repository is also mirrored there
if hash git &>/dev/null; then
if ! git clone --depth=1 https://gitea.evergreencrypto.co/EvergreenCrypto/docker-finance docker-finance/repo -b v1.3.0; then
if ! git clone --depth=1 https://gitea.evergreencrypto.co/EvergreenCrypto/docker-finance docker-finance/repo -b v1.4.1; then
echo "FATAL: docker-finance repo not cloned" >&2
fi
else

View File

@@ -372,6 +372,14 @@ Your `flow` directory will contain a symlink called `src` which links to code th
Before you try to infer market prices, be sure to fetch prices *before* you do your first import (or first import of the year). If you do not fetch, the prices journal will **not** be included within the import and, if you have a previous year of prices, **you will unwittingly infer against that previous year instead of your expected year!**
##### Caveats & Oddities: Flow: Accounts: Ledger
In the "Ledger Live" desktop app, change your wallet name to reflect your subaccount(s). They SHOULD be named with the format: `device_supertype:device_subtype:wallet_name-counter` in order to future-proof the number of devices and wallets that have the same name. For example:
1. You have 1 Ledger Nano S device with 2 bitcoin wallets ("spending" and "savings"). They would be named `nano:s-1:spending-1` and `nano:s-1:savings-1`
2. You have 1 Ledger Nano X device with 1 bitcoin wallet ("spending") and 1 ethereum wallet ("staking"). They would be named `nano:x-1:spending-1` and `nano:x-1:staking-1`
> Note: you can reuse "Ledger Live" wallet names across all chains because chains and symbols are added internally through `dfi` (i.e., you can name your bitcoin and ethereum wallets both `nano:x-1:spending-1`
##### Caveats & Oddities: Flow: Accounts: Trezor
In the "Trezor Suite" app, change your wallet name to your subaccount(s). For example, to delineate between your Trezor One from several Trezor T devices, and to delineate between their separate wallets *within* every device, follow these steps: