Paul Eggleton 43203c578c Record and display update logs ... At the moment it's a bit difficult to get update logs out of the environment in which the update script is being run. In order to make the logs more accessible, create a LayerUpdate model to record the output of update_layer.py separately for each layerbranch and tie the created LayerUpdates together with a single Update model per session. We provide two ways to look at this - a Tools->Updates page for logged-in users, and there's also an "Updates" tab on each layer that is accessible to anyone; which one is useful depends on whether you are looking at the index as a whole or an individual layer. Update records older than 30 days are deleted automatically by default. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>		2016-11-16 15:31:46 +13:00
..
__init__.py	layerindex/migrations: Add initial migration	2016-10-18 16:41:24 +13:00
0001_initial.py	layerindex/migrations: Add initial migration	2016-10-18 16:41:24 +13:00
0002_distro.py	layerindex: Add distro to web interface and model	2016-10-18 16:42:15 +13:00
0003_auto_20161011_0304.py	layerindex: Add collection and version to layerbranch	2016-10-18 16:42:16 +13:00
0004_layerdependency_required.py	layerindexer: Add layer recommends support	2016-10-18 16:42:16 +13:00
0005_layerupdate.py	Record and display update logs	2016-11-16 15:31:46 +13:00