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:
6 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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
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
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?
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?
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?
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
gcstar
GCSTAR(1) Linux User's Manual GCSTAR(1)
NAME
GCstar - Personal collection manager
SYNOPSIS
gcstar [-u UPDATE-OPTIONS] [-x EXECUTE-OPTIONS] [FILENAME]
DESCRIPTION
GCstar is a Gtk2 program used to manage personal collections.
OPTIONS
Without any option, it will open FILENAME if specified or the previously opened file. There are also two groups of options.
UPDATE-OPTIONS
-u, --update
Tell GCstar to look for available updates
-a, --all
Update all components
-c, --collection
Update collection models
-w, --website
Update plugins to download information
-i, --import
Update plugins to import data
-e, --export
Update plugins to export data
-l, --lang
Update translations
-n, --noproxy
Don't ask for a proxy
EXECUTE-OPTIONS
-x, --execute
Enter non-interactive mode
-c, --collection MODEL
Specify the collection type
-w, --website PLUGIN
Specify the plugin to use to download information
-i, --import PLUGIN
Specify the plugin to use to import a collection
-e, --export PLUGIN
Specify the plugin to use to export the collection
-f, --fields FILENAME
File containing fields list to use for import/export
-o, --output FILENAME
Write output in FILENAME instead of standard output
--download TITLE
Search for the item with TITLE as name
--importprefs PREFERENCES
Preferences for the import plugin
--exportprefs PREFERENCES
Preferences for the export plugin
Preferences for import/export plugins are specified using this schema
Key1=>Value1,Key2=>Value2
ENVIRONMENT
HOME Used to define following variables if needed
XDG_CONFIG_HOME
Where configuration files should be stored. If not defined: $HOME/.config
XDG_DATA_HOME
Where some data will be stored. If not defined: $HOME/.local/share
BUGS REPORTING
To report bugs, please use this forum:
http://forums.gcstar.org/viewforum.php?id=4
AUTHORS
Tian <tian@c-sait.net>
http://www.gcstar.org/
GCstar 17 August 2006 GCSTAR(1)