Opened 14 years ago
Last modified 14 years ago
#29 closed enhancement
Create data migrations for static models — at Version 3
| Reported by: | adehnert | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Initial Release |
| Component: | Core | Version: | |
| Keywords: | Cc: | ||
| Size: |
Description (last modified by adehnert)
At the moment, when you create a new deployment, you need to remember to create various static models. South should be poked to do this automatically.
This includes:
- OfficerRole?
- System users, groups, and associated permissions
- The system:groupadmin group and groupadmin@SYSTEM user
- mit, autocreated groups
- asa-ebm, mit-deskworker, mit-offices
- ActivityCategory? (though at least there's a script for this already; see #30)
There's probably some other stuff that I'm forgetting just now.
Change History (3)
comment:1 Changed 14 years ago by adehnert
- Summary changed from Create data migrations for OfficeRoles to Create data migrations for OfficerRoles
comment:2 Changed 14 years ago by adehnert
- Description modified (diff)
- Summary changed from Create data migrations for OfficerRoles to Create data migrations for static models
comment:3 Changed 14 years ago by adehnert
- Description modified (diff)
Note: See
TracTickets for help on using
tickets.
Fixtures may be more appropriate for OfficerRole? and ActivityCategory?.
(I think users, groups, and permissions do want a data migration, to handle foreign keys.)