Closed
Bug 731715
Opened 13 years ago
Closed 13 years ago
wiki: continuous migrations on stage9
Categories
(developer.mozilla.org Graveyard :: Editing, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
2.4
People
(Reporter: groovecoder, Assigned: groovecoder)
References
Details
(Whiteboard: u=contributor c=wiki p=2 2.4.5)
Migrate top 100 viewed, recently edited, longest, and non-english articles from MindTouch to Kuma on stage9 every 3 hours WITH the overwrite option.
Comment 1•13 years ago
|
||
We probably want another script run by cron like this one:
https://github.com/mozilla/kuma/blob/mdn/scripts/migrate_recent.sh
And the command in that new script should look something like:
python26 manage.py migrate_to_kuma_wiki --wipe --viewed=50 --recent=50 --longest=50 --nonen=50
That will delete all Kuma wiki docs, revisions, and tags. It will then migrate over the 50 most viewed, recently edited, longest, and non-english pages.
That should be a decent subset for banging on, without migrating over everything (ie. 30000 pages). If 50 of each of these doesn't end up being too server-intensve, we could bump them up to 100 or 200
If the cronjob runs a script, rather than this command directly, we always have the option to tweak things later with a git push.
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → lcrouch
Comment 2•13 years ago
|
||
Commit pushed to mdn_prod at https://github.com/mozilla/kuma
https://github.com/mozilla/kuma/commit/3e433cebc00673273a39dfc24769f5789e253c38
Bug 731715 migrate_top script; fix user attr bug during migration
Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•13 years ago
|
||
Comment 4•13 years ago
|
||
verified fixed https://developer-stage9.mozilla.org/en-US/docs/all
Status: RESOLVED → VERIFIED
Updated•13 years ago
|
Version: Kuma → unspecified
Updated•13 years ago
|
Component: Docs Platform → Editing
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•