549327 - Create a second stage for opentochoice.org 1.0 content

Status: VERIFIED FIXED

(mozilla.org Graveyard :: Server Operations, task)

Description

[Staś Małolepszy :stas]

Please create a second staging site for opentochoice.org

URL: opentochoice-content.stage.mozilla.com

You could see how this was done for opentochoice.stage.mozilla.com. I think there were a couple of edits in wp-config.php (setting WP_CONTENT_DIR, LANGDIR, maybe just copy it over?) and a new directory called opentochoice_content was created, to which projects/trunk/wp-content was checked out.

Please set up a DB for this new stage from a current dump of the DB on production. We will use this to test new content with the new theme.

Thanks!

For some background, here's a conversation I had with fox2mike:

16:49 stas> we have http://opentochoice.stage.mozilla.com/ and http://opentochoice.org/
16:51 stas> we're working on 2 (or 4) things now for tomorrow's launch
16:51 stas> 1. theme (+ l10n)
16:51 stas> 2. new blog posts (+ l10n)
16:52 stas> all new posts are in the prod's DB as drafts
16:52 stas> that's because we didn't want to write them on stage, and then have to migrate them from there (it's 20 posts times 12 localizations)
16:54 stas> now, there's an export feature but we can't use it, because it doesn't export the meta data about which post is a translation of which
16:54 stas> so, we have those posts in prod's DB and now we'd like to preview them (and QA the new site with the target content) on stage
16:55 stas> so you could just import prod's DB to stage, right?
16:55 fox2mike> okay
16:55 fox2mike> yeah, doable
16:55 stas> now, here's the catch
16:56 stas> on stage, we have a new theme, which is translated only on stage
16:56 stas> and the translations are in stage's DB
16:56 fox2mike> well
16:56 fox2mike> we'll dump stage
16:56 fox2mike> dump prod
16:56 fox2mike> push prod in
16:56 fox2mike> push the tables containing the themes etc from stage
16:57 fox2mike> if it's that simple
16:57 stas> that could work, yes
16:57 fox2mike> yeah
16:57 stas> looking at the schema of the theme's translations table
16:58 stas> foreign keys should be OK

16:58 stas> another solution, would be to create a new stage and use prod's DB with no modifications.
16:58 stas> then we can preview theme's l10n on stage1, and content (all of it, EN and l10n) on stage2
16:58 fox2mike> how are we getting all this to prod? 
16:59 stas> another process
16:59 stas> manual export of PO files which is the safest but also time consuming
16:59 stas> which is why I don't want to do this right now for stage.
16:59 fox2mike> the second option is a nicer one, in terms of easier to create
16:59 fox2mike> and no messing around
16:59 stas> so on stage2, we'd use new theme and prod's content, but with no theme translations
17:00 fox2mike> okay
17:00 stas> which will still be in stage1 DB

17:05 stas> there's also another catch
17:05 stas> :)
17:05 stas> wordpress stores the URL of the installation in wp-options table
17:06 stas> if we dump prod DB and use it on 2nd stage
17:06 fox2mike> siteurl and home
17:06 fox2mike> can be changed
17:06 stas> it might actually redirect to prod, still
17:06 stas> at least for wp-admin
17:06 stas> right
17:06 fox2mike> only in two places
17:06 fox2mike> that'll be updated
17:06 stas> so there needs to be a small edit of the imported DB

Comment 1

[Stephen Donner [:stephend] Not actively reading bugmail]

Sorry for raising this to critical, since you've already assigned it to yourself, Jeremy, but we need to get this going ASAP, since the certification of the final 1.0 website relies on this; thanks!

Comment 2

[Alex Buchanan [:abuchanan]]

Hey, we're running out of time for this.  Oremj, could we get an ETA?

Comment 3

[Jeremy Orem [:oremj]]

http://opentochoice2.stage.mozilla.com/

It's a dump of the production db with home and siteurl updated.

Comment 4

[Staś Małolepszy :stas]

Thanks!!

Comment 5

[Stephen Donner [:stephend] Not actively reading bugmail]

Verified FIXED (as best I understand, it has all we need).  Thanks.