Sponsored Content
The Lounge What is on Your Mind? VBulletin 3.8 to Discourse on Docker Migration Test Take Four Post 303045267 by Neo on Sunday 15th of March 2020 03:07:01 AM
Old 03-15-2020
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 "likes" (not sure if this part will work or not, first time test for this migration feature.)

Chuggin' along again, from total scratch on a new server (and with fingers crossed):

Code:
root@discourse1-app:/var/www/discourse# su discourse -c 'bundle exec ruby script/import_scripts/vbulletin_neo4.rb'
discourse:@localhost wants vb3
Loading existing groups...
Loading existing users...
Loading existing categories...
Loading existing posts...
Loading existing topics...

importing groups..
       20 / 20 (100.0%)  [173261 items/min]   
importing users
     4774 / 138160 (  3.5%)  [182 items/min]

Looks like the "user part" of the migration will take about 12 hours Smilie

Entry in discourse posts table, to set up "thanks" to "likes" migration:

Code:
 vbpostid                | integer                     |           |          |

Let's see if this new vbulletin_neo4.rb code works on the first attempt (if it does, that would be a pleasant surprise).

Note: Will not be migrating private messages (PMs) from vb to discourse in this test run and probably not in the final migration either.
 

7 More Discussions You Might Find Interesting

1. Web Development

Removing VBSEO for vbulletin – Reverting back to vbulletin URLs

Please note, this information was copied from vbseo.com, now showing a database error. This is posted for reference since vbSEO seems to be going out of business: If you ever need to uninstall vBSEO , you can use the following instructions. Make sure you carefully follow each step. Login... (37 Replies)
Discussion started by: Neo
37 Replies

2. Linux

Docker and pipework,ip with other subnet

Recently i found this for give to docker a "personal" ip ip addr del 10.1.1.133/24 dev eth0 ip link add link eth0 dev eth0m type macvlan mode bridge ip link set eth0m up ip addr add 10.1.1.133/24 dev eth0m route add default gw 10.1.1.1On container i did ... (0 Replies)
Discussion started by: Linusolaradm1
0 Replies

3. AIX

AIX - FC Switch migration, SAN Migration question!

I'm New to AIX / VIOS We're doing a FC switch cutover on an ibm device, connected via SAN. How do I tell if one path to my remote disk is lost? (aix lvm) How do I tell when my link is down on my HBA port? Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies

4. Shell Programming and Scripting

Problem in extracting yocto SDK for docker

Actually I was facing the following issue while building my Yocto SDK on Docker container sudo docker build --tag="akash/eclipse-che:6.5.0-1" --tag="akash/eclipse-che:latest" /home/akash/dockerimage.yocto.support/ Sending build context to Docker daemon 26.93MB Step 1/5 : FROM eclipse/cpp_gcc ... (3 Replies)
Discussion started by: Akash BHardwaj
3 Replies

5. Docker

Docker learning Phase-I

Hello All, I had recently learnt a bit of Docker(which provides containerization process). Here are some of my learning points from it. Let us start first with very basic question: What is Docker: Docker is a platform for sysadmins and developers to DEPLOY, DEVELOP and RUN applications ... (7 Replies)
Discussion started by: RavinderSingh13
7 Replies

6. 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

7. What is on Your Mind?

Under Consideration: Migrate the Forums to Discourse

Dear All, After being active on the Node-RED forum for the last few weeks, I have been very impressed with Discourse, and my eyes have been opened. https://www.discourse.org/ but not the paid /hosted offering, but using the open distribution: https://github.com/discourse/discourse ... (52 Replies)
Discussion started by: Neo
52 Replies
pomigrate2(1)						      Translate Toolkit 1.3.0						     pomigrate2(1)

NAME
pomigrate2 - Migrates PO files from an old version using new POT files. SYNOPSIS
pomigrate [options] from to new-templates Where from is a directory of existing PO files, to is the directory where the migrated PO files will be stored, and new-templates is the directory that contains the PO Template files. DESCRIPTION
pomigrate2 aims to move an existing translation to a new version based on updated PO Template files automatically without user interven- tion. Therefore it is ideal for when you are migrating many languages or migrating from related but divergent products eg Mozilla to Fire- fox. OPTIONS
-F, --use-fuzzy-matching use fuzzy algorithms when merging to attempt to match strings -C, --use-compendium create and use a compendium built from the migrating files -C, --use-compendium=some-compendium.po use an external compendium during the migration --no-wrap do not wrap long lines --locale set locale for newly born files -q, --quiet suppress most output -p, --pot2po use pot2po(1) instead of msgmerge(1) to migrate (you cannot use compendia) OPERATION
pomigrate2 makes use of the Gettext tools msgmerge or Translate Toolkits pot2po to perform its merging tasks. It firstly finds all files with the same name and location in the from directory as in the new-template directory and copies these to the to directory. If there is no file in the from directory to match one needed by the new-template directory then it will msgcat(1) all files in the from directory with the same name and copy them to the correct destination in the to directory. If all of that fails then msginit(1) is used to initialise any missing PO files. Lastly all the files in <to> are merged using msgmerge(1) or pot2po(1). This process updates the files to match the layout and messages in new-templates. Optionally, by using --use-compendium, a compendium of all the translations in from can be created to be used in the final merge process. BUGS
None known Translate Toolkit 1.3.0 pomigrate2(1)
All times are GMT -4. The time now is 04:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy