update todo.md
This commit is contained in:
parent
36d096a938
commit
b248461034
1 changed files with 0 additions and 12 deletions
12
TODO.md
12
TODO.md
|
|
@ -76,13 +76,6 @@ Eastern rather than a rolling window. This would avoid unnecessary refetches
|
|||
during the trading day and ensure a fetch shortly after close gets fresh data.
|
||||
Probably alleviated by the cron job approach.
|
||||
|
||||
## Cron timing for mutual fund NAVs
|
||||
|
||||
Tiingo publishes mutual fund NAVs after midnight ET. The server cron (currently
|
||||
8 PM ET weekdays) gets stock/ETF data same-day but mutual fund NAVs lag by one
|
||||
trading day. Consider pushing the cron to midnight ET or adding a second morning
|
||||
run for funds.
|
||||
|
||||
## On-demand server-side fetch for new symbols
|
||||
|
||||
Currently the server's SRF endpoints (`/candles`, `/dividends`, etc.) are pure
|
||||
|
|
@ -104,8 +97,3 @@ introduce some opacity to the process as we wait for candles (for example) to
|
|||
populate. This could be solved on the server by spawning a thread to fetch the
|
||||
data, then returning 202 Accepted, which could then be polled client side. Maybe
|
||||
this is a better long term approach?
|
||||
|
||||
## Server deployment
|
||||
|
||||
After committing and pushing changes, rebuild and deploy zfin-server on nas2.
|
||||
The server needs the `TIINGO_API_KEY` added to `/data/zfin/.env` on the host.
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue