The first half of migrating "thanks to likes' is done, and I have already created a matching postgres discourse user_actions table in vb mysql to transfer all user likes action to discourse postgres, so can migrate all user "thanks" from vb site to discourse.
Later, I will temporarily update discourse posts table and add vb postid column because that info is lost in migration (vbulletin postid != discourse posts id)
bbcode to markdown did not appear to work yet. Will need to fix this. This is the major obstacle at the moment. I am trying to avoid rewriting this.
I am thinking not to migrate PMs from vb to discourse, and start fresh.
Basically, getting closer to a great migration setup.
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)
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)
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)
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)
I don't know why, but the rendering of my code mucks up the spacing and indentation, despite being correct in the original file. I'm having issues getting the following script to run (specifically the nested script at the end of the docker command near the end of the script; I think I'm not passing... (2 Replies)
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)
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
LEARN ABOUT DEBIAN
pomigrate2
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)