Clean up migration scripts & remove syncdb step from the Getting Started::Django documentation
Assignee: lcrouch → nobody
Component: Administration → Website
QA Contact: administration → website
Typically we run syncdb and then schematic (via ./bin/update_stage.sh) on a brand new repo. What concrete steps should we do to clean up the project? I think the pattern is we dev on a project until it's staged. At that point the schema is fixed based on your models. Then changes to the schema are captured in migration files. These are scripted for deployment by our stage and prod update scripts in the bin directory.
Created attachment 502891 [details] [diff] [review] change to demo-room-intial migration to fix setup Here's a patch showing the changes I had to make for `schematic migrations/` to complete successfully after a syncdb on a new workstation. If we don't want to get rid of syncdb we may need to make these changes?
Attachment #502891 - Attachment mime type: application/octet-stream → text/plain
Attachment #502891 - Attachment is patch: true
syncdb is okay but need to fix the bad migration for fresh django install. also need to merge maintenance into master and bump up the demo studio migration numbers.
Summary: clean up migrations & stop using syncdb → clean up migrations
Assignee: nobody → lcrouch
Please be aware of changes from Bug#628443.
Assignee: lcrouch → server-ops
Component: Website → Server Operations: Web Content Push
Product: Mozilla Developer Network → mozilla.org
QA Contact: website → mrz
Target Milestone: 0.9.3 → ---
Version: unspecified → other
On stage9, need to run the SQL in migrations/08-fix-mozilla-typos.sql against MySQL.
mysql> UPDATE feeder_bundle SET shortname = 'updates-mozilla' WHERE shortname = 'updates-updates'; Query OK, 1 row affected (0.03 sec) Rows matched: 1 Changed: 1 Warnings: 0
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.