Sponsored Content
The Lounge What is on Your Mind? VBulletin 3.8 to Discourse on Docker Migration Test Take Two Post 303045262 by Neo on Saturday 14th of March 2020 08:11:04 PM
Old 03-14-2020
THIS METHOD DOES NOT WORK
  • Step 1: Dump vb database again and all attachments.
  • Step 2: Transfer to discourse host.
  • Step 3:
    Code:
    discourse=# alter table posts add column vbpostid integer;
    ALTER TABLE
    discourse=#

  • Step 4: Moved transferred files to shared directory in docker (shared between docker and host)
  • Step 5: Rebuild staging mysql DB in docker / discourse.
  • Step 5: Run modified vbulletin_neo3.rb migration script.
    Code:
    export IMPORT=1
    su discourse -c 'bundle exec ruby script/import_scripts/vbulletin_neo3.rb'


THIS METHOD DID NOT WORK

I think there are some unknown (to me) status counters for topics and posts, because I did not seem to reimport anything but the news topics / threads since the last import.

So, seems I have little choice if I want to refine (transfer likes, fix ICODE tags) is to start migration from scratch.

Let's see after this "does not seem to be working attempt" completes.

The problem seemed to be with postgres and the fact it is running outside the docker discourse app. But frankly, I don't have time or interest to analyze why this "brute force method" failed.

It's easy enough to start over with all lessons learned from the test migrations.
 

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. UNIX for Beginners Questions & Answers

Can't pass a variable representing the output of lsb_release to a docker dontainer

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)
Discussion started by: James Ray
2 Replies

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

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
PCIC(4)                                                    BSD Kernel Interfaces Manual                                                    PCIC(4)

NAME
pcic -- PC Card bridge driver SYNOPSIS
device pcic device pccard DESCRIPTION
The pcic driver provides support for older ISA and non-Yenta PCI PC Card bridges. The pcic driver supports most ExCA devices attached to the ISA bus or PCI devices that do not conform to the Yenta specification. The following ISA devices, or true clones, are supported in the current code. Intel i82365SL Step A Intel i82365SL Step B Intel i82365SL Step C Intel's original 16-bit PC Card controller. Intel i82365SL-DF Intel's last version of this device. 3.3V support was added. VLSI 82C146 An older VLSI part with some issues on some machines. Cirrus Logic PD-6710 Cirrus Logic PD-6720 Cirrus Logic PD-6722 Cirrus Logic's pcic controller. Compatible with the i82365SL Step C with the addition of a different 3.3V control. Ricoh RF5C296 Ricoh RF5C396 Ricoh's PC Card bridge chips. These are compatible with the i82365SL Step C, but with yet another different 3.3V con- trol. Vadem 365 Vadem 465 Compatible with i82365SL Step C. Vadem 468 Vadem 469 Like the earlier Vadem models, but with Vadem's own, incompatible, 3.3V control system. IBM PCIC IBM clone of the original i82365SL part, with its own ID register value. Has no 3.3V ability. Many other vendors made parts in this arena, but most of them were compatible with one of the above chipsets. The following PCI pcmcia bridges are supported: Cirrus Logic PD6729 Cirrus Logic PD6730 O2micro OZ6729 O2micro OZ6730 BUGS
This does not work at all at the moment. BSD July 9, 2002 BSD
All times are GMT -4. The time now is 10:30 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy