Closed Bug 882169 Opened 12 years ago Closed 12 years ago

set up a legacy data DB for old thimble

Categories

(Webmaker Graveyard :: DevOps, defect)

x86
macOS
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: michiel, Assigned: johns)

References

Details

(Whiteboard: s=2013w24 p=1)

we'll need a secondary database for the legacy "old thimble" data. This should be a MySQL instance, with a database called "LegacyThimble", into which we import the data that is currently hosted on the Moz google drive (currently accessible to jp, jbuck, humph, brett, pomax and sheeri). This has a table "api_page" that needs to be renamed: mysql>CREATE DATABASE LegacyThimble; mysql>CONNECT LegacyThimble; mysql>SOURCE webpagemaker_mozilla_com.2013.06.11.sql; mysql>RENAME TABLE api_page TO LegacyProjects; This will let us hook the legacy DB functionality added to thimble into this mysql instance and serve up old content through the new system without having to support the old application (hurray!)
Severity: normal → blocker
Status: NEW → ASSIGNED
See Also: → 880768
Whiteboard: s=2013w24 p=1
We'll use the same RDS instances, same thimble user/hosts/passwords. Importing the data now to LegacyThimble schema. thimble will have only select grants
this has all been set up to work beautifully. old thimble data on new thimble is staging-live. +9001 to JP for doing a "why is sequelize breaking everything" debug session, too.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.