Sponsored Content
The Lounge What is on Your Mind? VBulletin 3.8 to Discourse on Docker Migration Test Take Two Post 303045230 by Neo on Saturday 14th of March 2020 07:11:05 AM
Old 03-14-2020
Have decided to go with (in progress):

Code:
rake destroy:topics_all_categories

Then add new vbpostid field to posts table in discourse and import / migrate all topics and posts and attachments again.

This will take a long time. At least two days, I am guessing.

I made a full backup of the "almost working discourse app" first, so if this fails we can revert back to the last working instance.
 

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
DH_RUBY(1)																DH_RUBY(1)

NAME
dh_ruby - debhelper7 build system for Ruby software SYNOPSIS
dh_ruby [OPTIONS] DESCRIPTION
dh_ruby is a Debhelper 7 build system for Ruby software. It will automatically build and install files contained in Ruby packages, trying to work as close to Rubygems as possible but respecting Debian standards for Ruby packages. dh_ruby can automatically run your tests against all supported Ruby versions, see the "FILES" section below. See dh_ruby --help for details. OPTIONS
--clean, --configure, --build, --test, --install Commands called by debhelper at various steps of the build process. -h, --help Displays dh_ruby usage information. -v, --version Displays dh_ruby version information. --setuprb This option indicates that the build should use setup.rb rather than the usual gem-based build. To take effect, this option must come first ! ENVIRONMENT VARIABLES
DH_RUBY_IGNORE_TESTS This is a space-separated list of tests that dh_ruby will ignore during package build. The available test names are "require-rubygems" plus the names of all supported Ruby versions. At the time of writing, only "ruby1.8" and "ruby1.9.1" are supported. If set to "all", all tests will be ignored during the package build. DH_RUBY_USE_DH_AUTO_INSTALL_DESTDIR If this variable is defined (to anything), dh_ruby will respect the directory informed by dh_auto_install(1), usually debian/tmp. By default, gem2deb will install files to debian/package, where package is the first binary package listed in debian/control. This is useful for multi-binary source packages, where you will have all files installed to debian/tmp, and can them split the files into separate packages by using debian/package.install. DH_RUBY_GEMSPEC Determines which file contain the gem specification with package metadata. By default, dh_ruby will read metadata from a .gemspec file in the root of source package directory. You can use this variable to override that if want to provide custom metadata for the Debian package. In the case there are more than one .gemspec in the source package root, you will need to use DH_RUBY_GEMSPEC to instruct dh_ruby about which one to use. FILES
debian/ruby-test-files.yaml, debian/ruby-tests.rake, debian/ruby-tests.rb Theses files can be used to explicitly tell dh_ruby how to run the tests in your package. When running the tests, dh_ruby will automatically set RUBYLIB to include the appropriate directories where the package files were installed in your package to make sure the tests use them instead of the files in the source directory. Your package can only contain at most one of these files. debian/ruby-test-files.yaml must contain a YAML document with a list of test files to be run. If the package metadata contains an explicit list of test files, gem2deb(1) will automatically generate this file for you. Example from ruby-mime-types: --- - test/test_mime_type.rb - test/test_mime_types.rb debian/ruby-tests.rake can be used to run the tests with rake(1). If you use this file, your package must Build-Depend on the rake package. You can use anything you would use in a regular Rakefile, but you must define a default task. gem2deb includes utility test task that makes it easier for you by creating a default task automatically. Example: require 'gem2deb/rake/testtask' Gem2Deb:Rake::TestTask.new do |t| t.test_files = FileList['test/*_test.rb'] end If debian/ruby-tests.rb exists, it will be run with each supported Ruby version, and must finish with a exit status of 0, otherwise dh_ruby assumes the tests failed. A simple example: require 'test/unit' require 'mypackage' # if 'mypackage.rb' or 'mypackage.so' was not installed properly, this will fail class MyPackageTest < Test::Unit::TestCase def test_features assert_equal 4, MyPackage.sum(2,2) end end debian/require-rubygems.overrides Fine-tune the "require-rubygems" test. If the package has a very good reason to actually `require "rubygems"`, you can use this file as a whitelist of files allowed to have `require "rubygems"`. This file is expect to contain a YAML document with a list of files that must be ignored when checking for `require "rubygems"` lines. Example: --- - debian/ruby-foo/usr/lib/ruby/vendor_ruby/foo.rb - debian/ruby-foo/usr/lib/ruby/vendor_ruby/foo/rubygems.rg As you can see above, you have to list filenames based on their corresponding install locations in the package temporary install directory, i.e. `debian/${pkg}/..` SEE ALSO
gem2deb(1) COPYRIGHT AND AUTHORS
Copyright (c) 2011, Lucas Nussbaum <lucas@debian.org> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. 2012-05-17 DH_RUBY(1)
All times are GMT -4. The time now is 07:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy