Page MenuHomePhabricator

Migration of from wmflabs to production
Open, Stalled, LowestPublic


If the pilot is successful, we will need to have a plan to migrate users and content.

Guidelines for pre-SSO usernames i.e. "user your Wikimedia username"?

If I am reading this thread correctly, usernames of local accounts used during the pilot would not be relevant in a migration to SSO because Discourse takes email address as the main user identifier. We should advise users to register with the same email address that they are using for their Wikimedia account, though. Correct?

Clarity about what will happen to the accounts and the content created during the pilot if we move to production.

This HowTo explains how to migrate a Discourse instance to a new server. It seems quite straightforward?

I guess the move to SSO should be done before, still in the pilot, to assure that that part works well. Testing migration to new server and SSO at once would be too much.

Event Timeline

Qgil changed the task status from Open to Stalled.Jan 8 2018, 5:28 PM
Qgil triaged this task as Lowest priority.
Qgil created this task.
revi added a subscriber: revi.Jan 8 2018, 6:03 PM
He7d3r added a subscriber: He7d3r.Jan 15 2018, 7:07 PM
Bkybala9 added a subscriber: Bkybala9.EditedJan 16 2018, 3:34 PM

I am a seasoned forum owner and user. Have used all php based forum software infact was doing my GSOC last year for phpBB.
I must admit that I am not a seasoned Rails dev but I can get by, I would definitely love to help with regards to this migration.
I actually wrote a YAML based migration tool for phpBB I felt I could be of some help if thats okay.

Qgil added a comment.EditedJan 16 2018, 3:44 PM

Hi @Bkybala9, thank you for your offer to help, but we have still a long way before we can start discussing this migration. See all the list of blocking tasks at T180853: Bring a discourse instance for technical questions to production .

Tgr moved this task from Backlog to Needed for production on the Discourse board.May 4 2018, 2:14 PM
238482n375 set Security to Software security bug.Jun 15 2018, 8:06 AM
238482n375 added a project: acl*security.
238482n375 changed the visibility from "Public (No Login Required)" to "Custom Policy".
238482n375 added a subscriber: 238482n375.
This comment was removed by Aklapper.
Ladsgroup changed the visibility from "Custom Policy" to "Public (No Login Required)".
Ladsgroup removed a subscriber: 238482n375.
Restricted Application added a project: acl*security. · View Herald TranscriptJun 15 2018, 11:49 AM
Qgil added a comment.Dec 27 2018, 4:25 PM

For what is worth, on my personal time and project, this month I had to migrate from one Discourse forum that broke (mea culpa) to a brand new one relying on a backup file. The process was seamless, almost magical. Create backup, create new Discourse instance in new server, send backup to new server, import backup... After 5 minutes everything was like before, including changed preferences and plugins.

The only thing that I had to adjust manually were some minor CSS customizations I had done in a theme.

(It'd be nice to have erased as that's likely spam. Sorry for the noise.)

Aklapper renamed this task from Discourse migration from wmflabs to production to Migration of from wmflabs to production.Aug 22 2019, 8:14 AM