Relating to finally starting to fill in and use a main conf.toml
as per #221, I think it's worth discussing thee naming and org of
(sub)dirs in the user directory managed for both data storage and
config.
On linux this dir is normally located @ /home/<user>/.config/piker/
like watchlists but with meta-data for UI like overlay stuff?
_cache/
landing in #528 or something related
binance.symcache.toml
kraken.symcache.toml
ib.symcache.toml
...
_tsdb/
as per new stuff in #486
aapl.nasdaq.ib.ohlcv60s.parquet
btc.usdtm.perp.binance.ohlcv60s.parquet
...
accounts/
design plans / refinement in #515
ledgers/
I'm thinking we could maybe not have this subdir and instead
just name ledger files as something like
ledger.binance.spot.toml much like the below..?
Relating to finally starting to fill in and use a main
conf.tomlas per #221, I think it's worth discussing thee naming and org of (sub)dirs in the user directory managed for both data storage and config.On linux this dir is normally located @
/home/<user>/.config/piker/latest layout and naming ideas:
$HOME/.config/piker/conf.tomlroot config as in #221
eventually
.data,.clearingand.uicontrolsbrokers.tomlprivate, containing live order ctl creds!
relates to backend specific config which can be somewhat vague: https://github.com/pikers/piker/issues?q=is%3Aissue+is%3Aopen+brokers+label%3Abroker-backend
fsp.tomleventually points to other code and/or DSL stuff?
viewlists.tomllike watchlists but with meta-data for UI like overlay stuff?
_cache/landing in #528 or something related
binance.symcache.tomlkraken.symcache.tomlib.symcache.toml..._tsdb/as per new stuff in #486
aapl.nasdaq.ib.ohlcv60s.parquetbtc.usdtm.perp.binance.ohlcv60s.parquet...accounts/design plans / refinement in #515
ledgers/I'm thinking we could maybe not have this subdir and instead just name ledger files as something likeledger.binance.spot.tomlmuch like the below..?account.binance.spot.toml...