Search Results

Update1:


Now in data integrity testing phase: Please Help Integrity Test New Discourse Forums V2...

Update on Migration:

There is an old Chinese saying which goes something like this:

"You cannot see the entire mountain standing in the valley".

So, we asked our mod team to do some testing...

Update:

@Scrutinizer and @Neo are getting very close to requesting our team test the new forum. We are not there yet, but getting close:


@Scrutinizer has written some unique custom...

Update:


I have successfully moved all servers over to the "two container (data, web) with nginx reverse proxy to unix socket" configuration.
The problem was missing information in the support...

Update:

There is an anomaly regarding the rebuilding process (in the container) of the custom avatars in the "two container, nginx reverse proxy to unix socket" configuration.

See this post on...

Update:


Staging server is running the "two container, nginx reverse proxy to unix socket" configuration.

Future production server is running the "two container without nginx reverse proxy"...

Update:

After man days on this one issue, I have got the "two container" solution with nginx as a front end reverse proxy to a unix domain socket to work on the staging server.

There is a...

Update:

Have made some core changes and am currently running both our staging server and our production server in "two container" mode; where the database and the web app are in two separate...

Update:

Long baking (staging server, discourse1) done after close to 15 hours:

8292

It is much improved, but @Scrutiziner, with his eagle eye for details, has plans for more refinements to...

Update:

This migration is moving along. @Scrutinizer has been a great help with debugging the bbcode migration, writing Ruby methods to preprocess various bbcode situations which arise in the...

Another update:

We continue to make progress in the complex mess of migration the bbcode from the old forum to the new ones:


@Scrutinzer wrote some nice code which strips all bbcode from our...

It has been a few days since my last status update, so here is a new, quick one:

@Scrutiziner and @Neo continue to work on the migration and are getting closer. The migration script provided...

For those who have never seen the inside of a Discourse app, here are the canned raking tasks:


# rake --tasks
rake about # List...

Well, as a update, this earlier MariaDB REGEX was flawed, my bad.

UPDATE post SET pagetext= LOWER(REGEXP_REPLACE(pagetext,'\\[ATTACH\\](.*)\\[\\/ATTACH\\]',...

Update (from one hour ago):


Updated the new community sites with latest posts, new users, likes, etc. from legacy site.

Ran an early preprocessing script against the legacy DB.
...

According to a quick check 35 tables (posts with tables) has been stripped or skipped from the migration:


MariaDB [vb3]> select count(postid) from post where pagetext like '%[table="head"]%';...

Also, I am finding, by trial and error, that even before preprocessing with the Ruby migration scripts, there are some transformations which are easily done on the copy of the vB3 MySQL DB dump; for...

Update:

Change in direction (too slow to keep doing the migration over and over).

Create / write a Ruby script (done):


Retrieve the mappings from the vB posts to the Discourse posts...

Today, armed with a new migration script vbulletin_neo7.rb I will start a migration from scratch on the staging server for the purposes of getting raw preprocessed posts from the postgres DB and...

We "completed" the migration of this vB3 site to Discourse a number of days ago. However, deeper testing by @Scrutinizer and @MadeInGermany revealed that a lot of text was mangled in the migration. ...