| | 1 | Certain data in the database is loaded from an external source. While the Django admin can be used to manage this data, it's liable to result in your edits being overwritten. Here is some data that shouldn't be edited from Django: |
| | 2 | |
| | 3 | == Sources == |
| | 4 | |
| | 5 | Fixtures:: Stored in the $app/fixtures/ directories. Each time a migration is run, these will be reset. |
| | 6 | Data Migrations:: Stored in the $app/migrations/ directories. These will not be automatically reverted, but I'd like to keep them synced anyway. In some cases, these have cron jobs to monitor for changes. |
| | 7 | Moira:: Synced from various lists |
| | 8 | |
| | 9 | |
| | 10 | == Affected models or instances == |
| | 11 | |
| | 12 | * forms.FYSMCategory (fixture) |
| | 13 | * groups.ActivityCategory (fixture) |
| | 14 | * group classes, funding, statuses (one-time migration) |
| | 15 | * officer roles (one-time migration) |
| | 16 | * auth group existence and permissions (migration, with cron job) |
| | 17 | * autocreated, mit |
| | 18 | * asa-ebm |
| | 19 | * mit-sao, mit-offices, mit-deskworker |
| | 20 | * system:groupadmin |
| | 21 | * auth group membership (moira, via lists on asa-db-sync-lists) |
| | 22 | * staff status (moira, via asa-admin) |
