Damien De Paoli
e05b2c7b5b
* pulled old values of data via restic backups
* inserted them into a new finance_history table
* added a finplan user, use of sudo & better ENV (container/production) & wrapper.sh into Dockerfile (like I do for other projects)
* recalculate the bills / Living Expenses now we have real bills for a year
* remove tax back for now (need to handle quit date vs. end of financial year better)
* hard-coded / hacked in 2026 for pay cycle dates / should be dynamic, but not sure I'll work in 2027+
* refactor front-end to handle 2026 as the current year / its more or less dynamic (via hard-coded FIRST_YEAR) variable - could not use datetime, as it was in late Dec. when I noticed the issue ('next pay' was in 2026, current year was 2025)
* also added history to graphs, changed formatting to make the history /
* savings projections to be orannge with circles, but historical is a solid line, future is a dash, also made all lines have lineWidth: 1 for aesthetics
CONSIDER in real-world:
* moving > $250k into say ING, then rabo-bank -- 4 months interest higher in each -- maybe to another provider after that
while the balance is > $250k it offsets individual bank risk
* maybe buying shares in something like berkshire-hathaway, or vanguard ETFs?
* pay out car if the diff is negligible to reduce the exposure to > $250k in bank
To run the code:
cd ~/src/finplan
source ./.python/bin/activate
FLASK_APP=main ./.python/bin/flask --debug run --host=mara.ddp.net