Sponsored Content
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:
 

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
erl_tar(3erl)						     Erlang Module Definition						     erl_tar(3erl)

NAME
erl_tar - Unix 'tar' utility for reading and writing tar archives DESCRIPTION
The erl_tar module archives and extract files to and from a tar file. The tar file format is the POSIX extended tar file format specified in IEEE Std 1003.1 and ISO/IEC 9945-1. That is the same format as used by tar program on Solaris, but is not the same as used by the GNU tar program. By convention, the name of a tar file should end in " .tar ". To abide to the convention, you'll need to add " .tar " yourself to the name. Tar files can be created in one operation using the create/2 or create/3 function. Alternatively, for more control, the open , add/3,4 , and close/1 functions can be used. To extract all files from a tar file, use the extract/1 function. To extract only some files or to be able to specify some more options, use the extract/2 function. To return a list of the files in a tar file, use either the table/1 or table/2 function. To print a list of files to the Erlang shell, use either the t/1 or tt/1 function. To convert an error term returned from one of the functions above to a readable message, use the format_error/1 function. LIMITATIONS
For maximum compatibility, it is safe to archive files with names up to 100 characters in length. Such tar files can generally be extracted by any tar program. If filenames exceed 100 characters in length, the resulting tar file can only be correctly extracted by a POSIX-compatible tar program (such as Solaris tar ), not by GNU tar. File have longer names than 256 bytes cannot be stored at all. The filename of the file a symbolic link points is always limited to 100 characters. EXPORTS
add(TarDescriptor, Filename, Options) -> RetValue Types TarDescriptor = term() Filename = filename() Options = [Option] Option = dereference|verbose RetValue = ok|{error,{Filename,Reason}} Reason = term() The add/3 function adds a file to a tar file that has been opened for writing by open/1 . dereference : By default, symbolic links will be stored as symbolic links in the tar file. Use the dereference option to override the default and store the file that the symbolic link points to into the tar file. verbose : Print an informational message about the file being added. add(TarDescriptor, FilenameOrBin, NameInArchive, Options) -> RetValue Types TarDescriptor = term() FilenameOrBin = Filename()|binary() Filename = filename()() NameInArchive = filename() Options = [Option] Option = dereference|verbose RetValue = ok|{error,{Filename,Reason}} Reason = term() The add/4 function adds a file to a tar file that has been opened for writing by open/1 . It accepts the same options as add/3 . NameInArchive is the name under which the file will be stored in the tar file. That is the name that the file will get when it will be extracted from the tar file. close(TarDescriptor) Types TarDescriptor = term() The close/1 function closes a tar file opened by open/1 . create(Name, FileList) ->RetValue Types Name = filename() FileList = [Filename|{NameInArchive, binary()},{NameInArchive, Filename}] Filename = filename() NameInArchive = filename() RetValue = ok|{error,{Name,Reason}} <V>Reason = term() The create/2 function creates a tar file and archives the files whose names are given in FileList into it. The files may either be read from disk or given as binaries. create(Name, FileList, OptionList) Types Name = filename() FileList = [Filename|{NameInArchive, binary()},{NameInArchive, Filename}] Filename = filename() NameInArchive = filename() OptionList = [Option] Option = compressed|cooked|dereference|verbose RetValue = ok|{error,{Name,Reason}} <V>Reason = term() The create/3 function creates a tar file and archives the files whose names are given in FileList into it. The files may either be read from disk or given as binaries. The options in OptionList modify the defaults as follows. compressed : The entire tar file will be compressed, as if it has been run through the gzip program. To abide to the convention that a com- pressed tar file should end in " .tar.gz " or " .tgz ", you'll need to add the appropriate extension yourself. cooked : By default, the open/2 function will open the tar file in raw mode, which is faster but does not allow a remote (erlang) file server to be used. Adding cooked to the mode list will override the default and open the tar file without the raw option. dereference : By default, symbolic links will be stored as symbolic links in the tar file. Use the dereference option to override the default and store the file that the symbolic link points to into the tar file. verbose : Print an informational message about each file being added. extract(Name) -> RetValue Types Name = filename() RetValue = ok|{error,{Name,Reason}} Reason = term() The extract/1 function extracts all files from a tar archive. If the Name argument is given as " {binary,Binary} ", the contents of the binary is assumed to be a tar archive. If the Name argument is given as " {file,Fd} ", Fd is assumed to be a file descriptor returned from the file:open/2 function. Otherwise, Name should be a filename. extract(Name, OptionList) Types Name = filename() | {binary,Binary} | {file,Fd} Binary = binary() Fd = file_descriptor() OptionList = [Option] Option = {cwd,Cwd}|{files,FileList}|keep_old_files|verbose|memory Cwd = [dirname()] FileList = [filename()] RetValue = ok|MemoryRetValue|{error,{Name,Reason}} MemoryRetValue = {ok, [{NameInArchive,binary()}]} NameInArchive = filename() Reason = term() The extract/2 function extracts files from a tar archive. If the Name argument is given as " {binary,Binary} ", the contents of the binary is assumed to be a tar archive. If the Name argument is given as " {file,Fd} ", Fd is assumed to be a file descriptor returned from the file:open/2 function. Otherwise, Name should be a filename. The following options modify the defaults for the extraction as follows. {cwd,Cwd} : Files with relative filenames will by default be extracted to the current working directory. Given the {cwd,Cwd} option, the extract/2 function will extract into the directory Cwd instead of to the current working directory. {files,FileList} : By default, all files will be extracted from the tar file. Given the {files,Files} option, the extract/2 function will only extract the files whose names are included in FileList . compressed : Given the compressed option, the extract/2 function will uncompress the file while extracting If the tar file is not actually compressed, the compressed will effectively be ignored. cooked : By default, the open/2 function will open the tar file in raw mode, which is faster but does not allow a remote (erlang) file server to be used. Adding cooked to the mode list will override the default and open the tar file without the raw option. memory : Instead of extracting to a directory, the memory option will give the result as a list of tuples {Filename, Binary}, where Binary is a binary containing the extracted data of the file named Filename in the tar file. keep_old_files : By default, all existing files with the same name as file in the tar file will be overwritten Given the keep_old_files option, the extract/2 function will not overwrite any existing files. verbose : Print an informational message as each file is being extracted. format_error(Reason) -> string() Types Reason = term() The format_error/1 converts an error reason term to a human-readable error message string. open(Name, OpenModeList) -> RetValue Types Name = filename() OpenModeList = [OpenMode] Mode = write|compressed|cooked RetValue = {ok,TarDescriptor}|{error,{Name,Reason}} TarDescriptor = term() Reason = term() The open/2 function creates a tar file for writing. (Any existing file with the same name will be truncated.) By convention, the name of a tar file should end in " .tar ". To abide to the convention, you'll need to add " .tar " yourself to the name. Except for the write atom the following atoms may be added to OpenModeList : compressed : The entire tar file will be compressed, as if it has been run through the gzip program. To abide to the convention that a com- pressed tar file should end in " .tar.gz " or " .tgz ", you'll need to add the appropriate extension yourself. cooked : By default, the open/2 function will open the tar file in raw mode, which is faster but does not allow a remote (erlang) file server to be used. Adding cooked to the mode list will override the default and open the tar file without the raw option. Use the add/3,4 functions to add one file at the time into an opened tar file. When you are finished adding files, use the close function to close the tar file. Warning: The TarDescriptor term is not a file descriptor. You should not rely on the specific contents of the TarDescriptor term, as it may change in future versions as more features are added to the erl_tar module. table(Name) -> RetValue Types Name = filename() RetValue = {ok,[string()]}|{error,{Name,Reason}} Reason = term() The table/1 function retrieves the names of all files in the tar file Name . table(Name, Options) Types Name = filename() The table/2 function retrieves the names of all files in the tar file Name . t(Name) Types Name = filename() The t/1 function prints the names of all files in the tar file Name to the Erlang shell. (Similar to " tar t ".) tt(Name) Types Name = filename() The tt/1 function prints names and information about all files in the tar file Name to the Erlang shell. (Similar to " tar tv ".) Ericsson AB stdlib 1.17.3 erl_tar(3erl)
All times are GMT -4. The time now is 09:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy