Repository navigation
Kilo now knows where you are heading: set a goal weight and the dashboard shows how far it still is and roughly when you can reach it at your current pace. This release has a database migration, which runs by itself when the app starts.
What's new
- A goal weight. Under Settings you can set an optional goal weight. The chart shows it as a dashed line, and the axis stretches to include it.
- How far, and roughly when. The Current average box shows the goal and how many kilos are still to go. Hover over the box, tap it or tab to it to see when the goal can be reached. The estimate follows the change in your moving average over the last Goal date trend days (30 by default, set next to the goal). The chart's tooltip shows the same estimate under the goal.
- Honest about the estimate. No date is given when the trend is flat or heads the other way, when the goal would take more than five years, or while there are fewer days of data than the trend needs. Once your average passes the goal, the box says the goal is reached.
- Colours that follow your goal. With a goal set, the change boxes are green when they move towards it, whether you want to lose weight or gain it. Without a goal they work as before.
- On your public chart, if you want. A new Show my goal switch adds the goal to your public chart. It is off by default and needs Show my weight to be on.
- An About link on the public chart. The header of the public chart now links to the About page, on the right. It opens in a new tab, so a chart shown on another site stays where it is.
Translations
- The 11 new texts are machine-translated in all 14 languages. Corrections from native speakers are welcome (see TRANSLATING.md).
Self-hosting
- A new fail2ban jail,
kilo-probe. It bans an address for a day at its first request for a PHP, WordPress, phpMyAdmin, CGI or XML-RPC page, which Kilo never has. Scanners send their whole list within seconds, sokilo-notfoundbanned them only after they had finished. To use it, installdeploy/fail2ban/filter.d/kilo-probe.confand the updateddeploy/fail2ban/jail.d/kilo.local, then reload fail2ban. - The example logrotate rule explains how to keep every old log instead of 8 weeks.
- CI now also runs the tests on Python 3.15. The development tools were updated: pytest 9.2, coverage 7.17, Playwright 1.64.1 and ruff 0.17.3.
Upgrading
This release has a migration (0004: four new columns on the user table). It runs by itself when the app starts. Existing accounts get no goal, so nothing changes for them until they set one. There are no new requirements.
- Back up the database first, for example
sqlite3 instance/weight.db ".backup weight-before-1.5.0.db". git pull.pybabel compile -d translations(new texts in every language).- Restart the app.
Afterwards the About page shows v1.5.0, and sqlite3 instance/weight.db "SELECT * FROM alembic_version" shows 0004.
Full changelog: v1.4.0...v1.5.0