Ruby mysql2 error on migration

الدعم
1

Hi guys,

I’m trying to ue the vanilla_mysql.rb importer script to migrate my shitty forum to the awesome discourse platform. :slight_smile: However, when I execute the commands this happens:

root@discourse-app:/var/www/discourse# gem install mysql2 --platform=ruby
Building native extensions. This could take a while…
Successfully installed mysql2-0.4.6
1 gem installed

root@discourse-app:/var/www/discourse# bundle exec ruby script/import_scripts/vanilla_mysql.rb
script/import_scripts/vanilla_mysql.rb:1:in require': cannot load such file -- mysql2 (LoadError) from script/import_scripts/vanilla_mysql.rb:1:in ’
root@discourse-app:/var/www/discourse#

What am I doing wrong / how can I fix it? :frowning: I’m using the default docker container on a clean ubuntu 16.04 vps.

2

Try this inside the docker container:

apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libmysqlclient-dev
su discourse -c 'export IMPORT=1; bundle install --no-deployment --without test --without development --path vendor/bundle'
su discourse -c 'export IMPORT=1; bundle exec ruby script/import_scripts/vanilla_mysql.rb'
4 إعجابات
3

Thanks for your reply. Here is a short version of my output:

**root@discourse-app:/var/www/discourse#: su discourse -c 'export IMPORT=1; bundle install --no-deployment --without test --without development --path vendor/bundle'**
[[....]]
An error occurred while installing mysql2 (0.4.6), and Bundler cannot
continue.
Make sure that `gem install mysql2 -v '0.4.6'` succeeds before bundling.

**root@discourse-app:/var/www/discourse#: exec ruby script/import_scripts/vanilla_mysql.rb'**                               Could not find gem 'mysql2' in any of the gem sources listed in your Gemfile.
Run `bundle install` to install missing gems.

**root@discourse-app:/var/www/discourse#: bundle install**
[[....]]
Bundle complete! 96 Gemfile dependencies, 175 gems now installed.
Gems in the group development were not installed.
Bundled gems are installed into ./vendor/bundle.

**root@discourse-app:/var/www/discourse#: su discourse -c 'export IMPORT=1; bundle exec ruby script/import_scripts/vanilla_mysql.rb'**                               Could not find gem 'mysql2' in any of the gem sources listed in your Gemfile.
Run `bundle install` to install missing gems.

:confused:

4

You need to install a dependency for it to work. I guess it’s missing.

apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libmysqlclient-dev
4 إعجابات
5

Thank you so mutch Gerhard! :slight_smile: It worked, I owe you.

3 إعجابات
6

Hi

I am facing this same situation but I am having trouble issuing these su discourse -c commands, they ask me for a password. I don’t think I created this user, it comes with the Docker container, so how do I get its password? Or how do I avoid being asked for one?

Thanks!

7

Is this a development install, an install from the standard guide, or something else?

If it’s from the standard guide you shouldn’t be prompted for a password when using su discourse -c from within the container.

إعجاب واحد (1)
8

Thanks, your confirmation that I “shouldn’t be prompted” sent me searching again, this time in a slightly different direction…

And I solved it! I was using a scripted command to enter the container that had slightly different options than the standard ./launcher enter app. One of them (maybe the absence of the --login option?) was causing this difference in behavior.

Anyway I am going to make sure I always use ./launcher going forward, there’s lots of stuff in there. Once again, thanks for your answer.

9

Another tip that might be useful for anyone else coming into this thread:

Using that command given above with IMPORT=1 will trigger this part of your Gemfile:

if ENV["IMPORT"] == "1"
  gem 'mysql2'
  gem 'redcarpet'
  gem 'sqlite3', '~> 1.3.13'
  gem 'ruby-bbcode-to-md', github: 'nlalonde/ruby-bbcode-to-md'
  gem 'reverse_markdown'
  gem 'tiny_tds'
end

I ran into problems with the installation of tiny_tds, and then with another thing it depends on called FreeTDS. After some wasted time on this I realized these are useful only for MS SQL imports, which I won’t be using, so I simply commented out the tiny_tds line in my Gemfile.

(it would be nice to have a comment in front of each of those packages saying what they are used for, if anyone knows)

إعجابَين (2)
11

مرحباً. أواجه نفس المشكلة هنا عند تشغيل هذا البرنامج النصي ولكن هذه الأوامر لا تساعد… هذا هو الناتج الذي أحصل عليه عند محاولة تشغيل su discourse -c 'export IMPORT=1; bundle exec ruby script/import_scripts/vanilla_mysql.rb':

root@ip-xxx-xx-xx-xx-app:/var/www/discourse# su discourse -c 'export IMPORT=1; bundle exec ruby script/import_scripts/snuffhouse.rb'
أنت تحاول التثبيت في وضع النشر بعد تغيير
ملف Gemfile الخاص بك. قم بتشغيل `bundle install` في مكان آخر وأضف
ملف Gemfile.lock المحدث إلى التحكم في الإصدار.

إذا كان هذا جهاز تطوير، فقم بإزالة تجميد /var/www/discourse/Gemfile
عن طريق تشغيل `bundle config unset deployment`.

تغيرت قائمة المصادر
تغيرت التبعيات في ملف Gemfile الخاص بك

لقد أضفت إلى ملف Gemfile:
* mysql2
* redcarpet
* sqlite3 (~> 1.3, >= 1.3.13)
* ruby-bbcode-to-md
* reverse_markdown
* tiny_tds
* csv
12

مرحباً، لقد قمت بحل هذه المشكلة ونسيت الرد هنا. الأمر هو أنني كنت أحاول تشغيل نص ترحيل لمنتدى يستخدم mysql وواجهت بعض الأخطاء. لكنني اتبعت الخطوات التالية وعملت بشكل جيد:

  • داخل جهاز docker الخاص بك حيث يعمل Discourse:
# الدخول إلى دليل المشروع
cd /var/www/discourse

# تثبيت تبعيات MySQL
apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libmariadb-dev

# تثبيت مكتبات MySQL (تصدير = 1)
su discourse -c 'export IMPORT=1; bundle install'

# تشغيل النص الخاص بك (vanilla_mysql في هذه الحالة)
su discourse -c 'export IMPORT=1; bundle exec ruby script/import_scripts/vanilla_mysql.rb'

لقد قمت بتنفيذ هذا على جهاز جديد اضطررت إلى إعداده وعمل بشكل جيد.