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
20 lines
932 B
Plaintext
20 lines
932 B
Plaintext
bills:
|
|
bills html, and growth types are poor code repitition / lame... could I do something more like:
|
|
{% for gt in growth %}
|
|
{% if gt.name == 'Min' %}
|
|
<option value='min'
|
|
{% if bt.which_growth == gt.name %}selected{% endif %}
|
|
>{{'%.2f'|format(bt.ann_growth_min)}}% {{gt.name}}</option>
|
|
|
|
CALC:
|
|
* if I quit at different times of the financial year, technically the amount I earn will be taxed
|
|
differently, but hard to calc - slides around with tax brackets in future
|
|
|
|
* still get double health insurance bills sometimes (just viewing a new date might trigger this??? or at least when I changed years)
|
|
|
|
UI:
|
|
* add FIXED Annotations:
|
|
* historical annotations (at least M_quit_date, Trip_date, school_fees in 25)
|
|
* should try AI with how to distribute annotations better
|
|
* make bills tabs a vertical navbar instead of horizontal
|