I’m trying to ue the vanilla_mysql.rb importer script to migrate my shitty forum to the awesome discourse platform. 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? I’m using the default docker container on a clean ubuntu 16.04 vps.
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.
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, 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.
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)
Hola. Estoy teniendo el mismo problema aquí al ejecutar este script, pero esos comandos no están ayudando… Esta es la salida que obtengo al intentar ejecutar 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'
Estás intentando instalar en modo de implementación después de cambiar
tu Gemfile. Ejecuta `bundle install` en otro lugar y añade el
Gemfile.lock actualizado al control de versiones.
Si esta es una máquina de desarrollo, elimina la congelación de /var/www/discourse/Gemfile
ejecutando `bundle config unset deployment`.
La lista de fuentes cambió
Las dependencias en tu gemfile cambiaron
Has añadido al Gemfile:
* mysql2
* redcarpet
* sqlite3 (~> 1.3, >= 1.3.13)
* ruby-bbcode-to-md
* reverse_markdown
* tiny_tds
* csv
Hola, he solucionado esto y olvidé responder aquí. La cuestión es que estaba intentando ejecutar un script de migración para un foro que usa mysql y me encontraba con algunos errores. Pero acabo de seguir los siguientes pasos y ha funcionado bien:
Dentro de tu docker-machine donde se está ejecutando Discourse:
# Entra en el directorio del proyecto
cd /var/www/discourse
# Instala las dependencias de MySQL
apt-get update && DEBIAN_FRONTEND=noninteractive apt-get install -y libmariadb-dev
# Instala los gems de MySQL (export = 1)
su discourse -c 'export IMPORT=1; bundle install'
# Ejecuta tu script (vanilla_mysql en este caso)
su discourse -c 'export IMPORT=1; bundle exec ruby script/import_scripts/vanilla_mysql.rb'
Acabo de hacer esto en una máquina nueva que tuve que levantar y funcionó perfectamente.