Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Update on vB3 Migration to Discourse - Issues and Status of BBCode Transformations
The Lounge What is on Your Mind? Update on vB3 Migration to Discourse - Issues and Status of BBCode Transformations Post 303045818 by Neo on Tuesday 14th of April 2020 04:48:22 AM
Old 04-14-2020
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 conversion to markdown.

For examples:

There was some newlines being added to code blocks, so we added some post-processing REGEX search and replace to tidy these up. This was a purely cosmetic change but @Scrutinizer is more annoyed by these cosmetic details than me, and so he wrote some Ruby code to fix it. We are very fortunately to have @Scrutinizer working with me on this.

The same is true for some "bbcode abuse" where in the past over the years, some people copy-and-pasted some bbcode into the forum or others just loved bbcode so much the embedded bbcode everywhere, sometimes nesting bbcode is strange ways. We have also slayed most of those dragons.

We are getting very close. We cannot promise 100% of every possible combination of bbcode-mangles in the vB3 forum will be perfect, but it will be very good, a few orders of magnitude from the initial release, hands down.

Currently I am rebaking all the post again on the staging server. That is a process which takes 12 to 14 hours. For those who may not be familiar with this, here is a short summary:

The vB3 forum (indeed most, if not all, LAMP-based forums) process(es) the pagetext in the database on the fly (when the page is summoned by the client, e.g. the web browser).

However, Discourse stores the pagetext as "raw" and then it cooks the raw into HTML to be rendered. This of course makes the site faster since the code is already rendered and stored in the DB "cooked".

The downside to this, of course, is that it takes longer to "cook all this" during migration testing (reprocessing the raw for bbcode mangling); but lucky for us, after migration is done, it's done.

BTW, this is the same way I serve our forumman pages. Man pages are also cooked and the cooked pages are stored in the DB to make them render faster, so this technique is nothing new.

OBTW, those man pages will stay here in the legacy vB3 forums; until we decide if and/or when to write a plugin to port these to discourse.

That's it for now.
This User Gave Thanks to Neo For This Post:
vgersh99
 

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Shell Script migration issues

Hi All, We will be doing a Solaris 8 to Solaris 10 migration migration, just wanted to know if there are any known / common issues arise from this migration from Shell script point of view. I tried searching this site but mostly post are related to SA's question and jumpstart, etc. If there's... (4 Replies)
Discussion started by: arvindcgi
4 Replies

2. HP-UX

Migration - Compiler Issues.

All, We are migrating an application from HP-UX B.11.00 to HP-UX B.11.31 and both of them have the same informix version - 7.25se. However the compilers are different on both servers. HP-UX B.11.00 - has B3913DB C.03.33 HP aC++ Compiler (S800) HP-UX B.11.31 - has PHSS_40631 1.0 HP C/aC++... (2 Replies)
Discussion started by: helper
2 Replies

3. Programming

How to track table status delete/update/insert status in DB2 V10 z/os?

Dear Team I am using DB2 v10 z/os database . Need expert guidance to figure out best way to track table activities ( Ex Delete, Insert,Update ) Scenario We have a table which is critical and many developer/testing team access on daily basis . We had instance where some deleted... (1 Reply)
Discussion started by: Perlbaby
1 Replies

4. What is on Your Mind?

Status of Migration of Moderation Systems

First a bit of history .... A number of years ago one of our admins built a number of plugin systems for moderation, including (1) a voting system, (2) a "user feelings" system and (3) a confidential posting system. During this time, I was busy on other projects, not very active in the forums,... (1 Reply)
Discussion started by: Neo
1 Replies

5. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Two

OK. Like we all do, we learn a lot from tests, test migrations, and so forth. Today, I started from scratch on test migration 2, armed with a lot more knowledge, The main differences are as follows: Installed discourse plugin ruby-bbcode-to-md before starting the install Modified... (30 Replies)
Discussion started by: Neo
30 Replies

6. What is on Your Mind?

VBulletin 3.8 to Discourse on Docker Migration Test Take Four

Test Build 4 on New Server, with changes identified in discourse test builds 2 and 3, primarily: Insuring ruby-bbcode-to-markdown is enabled. Removing line breaks from ICODE to markdown in migration script. Added vbpostid to posts in discourse to setup migrating vb "thanks" to discourse... (28 Replies)
Discussion started by: Neo
28 Replies

LEARN ABOUT DEBIAN

tspi_key_createmigrationblob

Tspi_Key_CreateMigrationBlob(3) 		     TCG Software Stack Developer's Reference			   Tspi_Key_CreateMigrationBlob(3)

NAME

       Tspi_Key_CreateMigrationBlob - create a key blob suitable for migrating to another TPM.

SYNOPSIS

       #include <tss/platform.h>
       #include <tss/tcpa_defines.h>
       #include <tss/tcpa_typedef.h>
       #include <tss/tcpa_struct.h>
       #include <tss/tss_typedef.h>
       #include <tss/tss_structs.h>
       #include <tss/tspi.h>

       TSS_RESULT Tspi_Key_CreateMigrationBlob(TSS_HKEY hKeyToMigrate,		TSS_HKEY hParentKey,
					       UINT32	ulMigTicketLength,	BYTE*	 rgbMigTicket,
					       UINT32*	pulRandomLength,	BYTE**	 prgbRandom,
					       UINT32*	pulMigrationBlobLength, BYTE**	 prgbMigrationBlob);

DESCRIPTION

       Tspi_Key_CreateMigrationBlob  returns a key blob containing an encrypted section, which will be different depending on the migration scheme
       indicated within the migration ticket previously created by the method Tspi_TPM_AuthorizeMigrationTicket().

PARAMETERS

   hKeyToMigrate
       Handle of the key object to migrate.

   hParentKey
       Handle to the parent key related to the key addressed by hKeyToMigrate.

   ulMigTicketLength
       The length (in bytes) of the rgbMigTickey parameter.

   rgbMigTicket
       Pointer to memory containing the migration ticket (migration public key and its authorization digest).

   pulRandomLength
       On successful completion this parameter returns the random data length returned at the parameter prgbRandom.

   prgbRandom
       On successful completion this parameter returns the random data.

   pulMigrationBlobLength
       On successful completion this parameter returns the length of the migration blob data returned at the parameter prgbMigrationBlob.

   prgbMigrationBlob
       On successful completion this parameter returns the migration data blob.

RETURN CODES

       Tspi_Key_CreateMigrationBlob returns TSS_SUCCESS on success, otherwise one of the following values are returned:

       TSS_E_INVALID_HANDLE - Either hKeyToMigrate, hParentKey or rgbMigTicket are invalid parameters.

       TSS_E_BAD_PARAMETER - One of the passed parameters is wrong.

       TSS_E_KEY_NO_MIGRATION_POLICY - No migration policy picked.

       TSS_E_INTERNAL_ERROR - An error occurred internal to the TSS.

CONFORMING TO

       Tspi_Key_CreateMigrationBlob conforms to the Trusted Computing Group Software Specification version 1.1 Golden

SEE ALSO

       Tspi_Key_CreateKey(3), Tspi_Key_CertifyKey(3).

TSS 1.1 							    2004-05-26					   Tspi_Key_CreateMigrationBlob(3)
All times are GMT -4. The time now is 02:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy