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 NETBSD
dh_strip
DH_STRIP(1) Debhelper DH_STRIP(1)
NAME
dh_strip - strip executables, shared libraries, and some static libraries
SYNOPSIS
dh_strip [debhelperoptions] [-Xitem] [--dbg-package=package] [--keep-debug]
DESCRIPTION
dh_strip is a debhelper program that is responsible for stripping executables, shared libraries, and static libraries that are not used for
debugging.
This program examines your package build directories and works out what to strip on its own. It uses file(1) and file permissions and
filenames to figure out what files are shared libraries (*.so), executable binaries, and static (lib*.a) and debugging libraries (lib*_g.a,
debug/*.so), and strips each as much as is possible. (Which is not at all for debugging libraries.) In general it seems to make very good
guesses, and will do the right thing in almost all cases.
Since it is very hard to automatically guess if a file is a module, and hard to determine how to strip a module, dh_strip does not
currently deal with stripping binary modules such as .o files.
OPTIONS
-Xitem, --exclude=item
Exclude files that contain item anywhere in their filename from being stripped. You may use this option multiple times to build up a
list of things to exclude.
--dbg-package=package
This option is a now special purpose option that you normally do not need. In most cases, there should be little reason to use this
option for new source packages as debhelper automatically generates debug packages ("dbgsym packages"). If you have a manual
--dbg-package that you want to replace with an automatically generated debug symbol package, please see the --dbgsym-migration option.
Causes dh_strip to save debug symbols stripped from the packages it acts on as independent files in the package build directory of the
specified debugging package.
For example, if your packages are libfoo and foo and you want to include a foo-dbg package with debugging symbols, use dh_strip
--dbg-package=foo-dbg.
This option implies --no-automatic-dbgsym and cannot be used with --automatic-dbgsym or --dbgsym-migration.
-k, --keep-debug
This option is a now special purpose option that you normally do not need. In most cases, there should be little reason to use this
option for new source packages as debhelper automatically generates debug packages ("dbgsym packages"). If you have a manual
--dbg-package that you want to replace with an automatically generated debug symbol package, please see the --dbgsym-migration option.
Debug symbols will be retained, but split into an independent file in usr/lib/debug/ in the package build directory. --dbg-package is
easier to use than this option, but this option is more flexible.
This option implies --no-automatic-dbgsym and cannot be used with --automatic-dbgsym.
--dbgsym-migration=package-relation
This option is used to migrate from a manual "-dbg" package (created with --dbg-package) to an automatic generated debug symbol
package. This option should describe a valid Replaces- and Breaks-relation, which will be added to the debug symbol package to avoid
file conflicts with the (now obsolete) -dbg package.
This option implies --automatic-dbgsym and cannot be used with --keep-debug, --dbg-package or --no-automatic-dbgsym.
Examples:
dh_strip --dbgsym-migration='libfoo-dbg (<< 2.1-3~)'
dh_strip --dbgsym-migration='libfoo-tools-dbg (<< 2.1-3~), libfoo2-dbg (<< 2.1-3~)'
--automatic-dbgsym, --no-automatic-dbgsym
Control whether dh_strip should be creating debug symbol packages when possible.
The default is to create debug symbol packages.
--ddebs, --no-ddebs
Historical name for --automatic-dbgsym and --no-automatic-dbgsym.
--ddeb-migration=package-relation
Historical name for --dbgsym-migration.
NOTES
If the DEB_BUILD_OPTIONS environment variable contains nostrip, nothing will be stripped, in accordance with Debian policy (section 10.1
"Binaries"). This will also inhibit the automatic creation of debug symbol packages.
The automatic creation of debug symbol packages can also be prevented by adding noautodbgsym to the DEB_BUILD_OPTIONS environment variable.
However, dh_strip will still add debuglinks to ELF binaries when this flag is set. This is to ensure that the regular deb package will be
identical with and without this flag (assuming it is otherwise "bit-for-bit" reproducible).
CONFORMS TO
Debian policy, version 3.0.1
SEE ALSO
debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
11.1.6ubuntu2 2018-05-10 DH_STRIP(1)