Patrick Williams | c0f7c04 | 2017-02-23 20:41:17 -0600 | [diff] [blame] | 1 | # Fixtures directory |
| 2 | |
| 3 | Fixtures are data dumps that can be loaded into Toaster's database to provide |
| 4 | configuration and data. |
| 5 | |
| 6 | In this directory we have the fixtures which are loaded the first time you start Toaster. |
| 7 | This is to provide useful default values and metadata to Toaster. |
| 8 | |
| 9 | - settings.xml This Contains Toaster wide settings, such as the default values for |
| 10 | certain bitbake variables. |
| 11 | |
| 12 | - poky.xml This is the default release data for supported poky based setup |
| 13 | |
| 14 | - oe-core.xml This is the default release data for supported oe-core based setups |
| 15 | |
| 16 | # Custom data/configuration |
| 17 | |
| 18 | - custom.xml |
| 19 | |
| 20 | To add custom initial data/configuration to Toaster place a file called |
| 21 | "custom.xml" in this directory. If present it will be loaded into the database. |
| 22 | We suggest that this is used to overlay any configuration already done. |
| 23 | All objects loaded with the same primary keys overwrite the existing data. |
| 24 | Data can be provided in XML, JSON and if installed YAML formats. |
| 25 | |
| 26 | # To load data at any point in time |
| 27 | |
| 28 | Use the django management command manage.py loaddata <your fixture file> |
| 29 | For further information see the Django command documentation at: |
| 30 | https://docs.djangoproject.com/en/1.8/ref/django-admin/#django-admin-loaddata |