v0.93

Upgrading:

Due to DB changes migrations must be run when upgrading from previous versions - this is as simple as running "./manage.py migrate" after pulling from the repo or installing the new version.

If there are errors running the above command after this release, you may have corrupt Prices in your database. See readme under "Schema Changes" for details.

Major changes - Simplified Prices:

Prices have now been fully detached from the Product model, and can now be added and edited via the Ingredient admin interface (below the nutritional data).

The product model still exists, but is now deprecated; it has no current purpose except to associate brand names with ingredients. If you don't care about that (it's not visible outside the admin anyway), products can be all safely deleted via the admin interface (use the checkbox to "select all" and then drop-down action box to "delete selected"). They should not have any performance effects from leaving them there, as no calculations use product objects.

Other changes:

Everything mentioned in the previous release probably counts, as it was only yesterday. They were only done as separate releases for Schema/API/Deprecation purposes.

Known Issues:

• Login/Logout and all data entry can only be done via the admin interface.

v0.92

Upgrading:

Due to DB changes migrations must be run when upgrading from previous versions - this is as simple as running "./manage.py migrate" after pulling from the repo or installing the new version. See readme under "Schema Changes" for details.

Updated Requirements:

This version is compatible with Django 3.x (previous used deprecated methods from version 1.x). The minimum Django version is now 2.2 LTS.

Major changes - Simplified Prices:

Prices are changing from being set on a Product to directly being set on an Ingredient, to simplify both the user interface and the code. As of this version, Price is attached to both Product and Ingredient. Prices will be linked to Ingredients automatically when running the above migrate command, so no manual changes are required to existing data.

Future versions will make Price settable via the Ingredient section of the admin interface rather than Product, and a release after that will possibly remove "Products" completely unless they can find a new purpose.

Other changes:

• Recipe "flags" have been added. These differ from Tags in two ways - each recipe can have only one flag, but flags are much more visible (being shown in lists etc). The intended use case is to mark recipes which are OK for general use to differentiate them from recipes which aren't working and need further changes and testing, or outdated recipes no longer recommended. However, they can be used for whatever the admin wants.
• "Rank" calculation changed to better take protein not used for energy into account.
• Tags for Recipe and Ingredient can now have a brief text description which is shown in list view when that tag is selected.
• The cost per kg (not just per-serve) of each recipe is now shown in the list view and CSV export
• $/kg of each recipe component is also shown in the detail view
• Recipe components are now selected through a pop-up search page rather than the old drop-down box
• Ingredient detail page now has a list of prices (from each supplier)
• Home page now shows what proportion of today's calories came from protein/fat/carbohydrates
• Fixes for assorted errors from zero-calorie ingredients (e.g. plain water)
• Recipe method textbox finally lets you keep your linebreaks
• Various minor bugfixes, optimizations and tweaks

Known Issues:

• Login/Logout and all data entry can only be done via the admin interface.

v0.91

Upgrading:

Due to DB changes migrations must be run when upgrading from 0.9 (see readme for details, but this is as simple as running "./manage.py migrate" after pulling from the repo).

Major changes:

• Quantity in recipe components now has separate "servings" and "weight" like diary does, rather than assuming one for ingredients and another for recipes. Now the amount of either a recipe or ingredient can be specified either way.
  • Note that weight is NOT crystallized from servings like in the diary, so if specifying the amount of something by servings in a recipe that amount will change if the component changes the amount it defines as a serving. This is intentional.
• Target visualisation improvements, including a green/yellow/red progress bar showing how far each nutrient is to the min/max targets, and comparing the per-serve nutrients against the current target in detail pages for recipes and ingredients.

Known Issues:

• Login/Logout and all data entry can only be done via the admin interface.

v0.9

Initial public release.

Known issues:

• Product view does not show all data it should.
• Default target progressbars only appear on home page (not diary or ingredient/recipe pages)
• Login/Logout only works via the admin interface
• per-serve/per-weight dichotomy in specifying the amount of a recipe included in another recipe (vs ingredients)