How to install discourse-tagging plugin manually for non docker instances

(Raul ) #1

Hi all,

At a first glance I could not find info regarding how to install the discourse-tagging plugin for non docker instances , I mean some steps in how to proceed to manually install this plugin, (I remember the previous plugin called discourse-plugin-tagger had some README instructions for this), will appreciate a lot if someone can give some hints here, obviously I am not used to work with ruby …

So far I guess should be something like:

cd path/discourse/plugins
git clone   # clone the repo here
cd ..
export RAILS_ENV=production                 # set to productions
rake ??????????              # copy migrations
rake db:migrate SCOPE=????                # run migrations
rake assets:precompile                      # precompile assets

Thanks in advance, and looking forward to have some info



No just edite app.yml like this

    - exec:
        cd: $home/plugins
          - mkdir -p plugins
          # Docker Manger
          - git clone
          # tagging plugin
          - git clone

and repuild your app

(Raul ) #3


Sorry maybe it’s me doing something wrong, but there is no app.yml on the filesystem so the next command outputs nothing:

find . -type f -iname "app.yml"

As I said in the beginning I am not running on docker, so I guess is because of this.

If I just clone the code of the plugin in the directory plugins like this:

git clone discourse/plugins/discourse-tagging

And then when trying to migrate the db I got this:

RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ENV=production bundle exec rake db:migrate --trace
rake aborted!
NoMethodError: undefined method `enabled_site_setting' for #<Plugin::Instance:0x000000020ecde0>
/fjord/discourse/plugins/discourse-tagging/plugin.rb:7:in `activate!'
/fjord/discourse/lib/plugin/instance.rb:171:in `instance_eval'
/fjord/discourse/lib/plugin/instance.rb:171:in `activate!'
/fjord/discourse/lib/discourse.rb:84:in `block in activate_plugins!'
/fjord/discourse/lib/discourse.rb:84:in `each'
/fjord/discourse/lib/discourse.rb:84:in `activate_plugins!'
/fjord/discourse/config/application.rb:154:in `<class:Application>'
/fjord/discourse/config/application.rb:19:in `<module:Discourse>'
/fjord/discourse/config/application.rb:18:in `<top (required)>'
/fjord/discourse/Rakefile:5:in `require'
/fjord/discourse/Rakefile:5:in `<top (required)>'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/rake_module.rb:28:in `load'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/rake_module.rb:28:in `load_rakefile'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:687:in `raw_load_rakefile'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:94:in `block in load_rakefile'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:176:in `standard_exception_handling'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:93:in `load_rakefile'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:77:in `block in run'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:176:in `standard_exception_handling'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:75:in `run'
/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/bin/rake:33:in `<top (required)>'
/fjord/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `load'
/fjord/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `<main>'



Folow this

cd /var/discourse
nano containers/app.yml

And add after docker maneger plugin

      - git clone

save and exite

./launcher rebuild app

(Raul ) #5

Sorry @Qasem_h I really appreciate your help, but I am not running on docker

The idea is do the upgrade to later on move the content to a Discourse on a docker in order to be aligned with the “official” way to install it, but in the meantime I have the application running on a Debian and there are no containers there.

That is why I was requesting since the beginning a manual way to do the installation of the plugin


(Robin Ward) #6

If you are seeing undefined method enabled_site_setting it’s because your version of Discourse is not recent enough to support the hooks that discourse-tagging needs.

You should remove the plugin, upgrade your discourse instance to a recent version, then try installing it again.

There are no migrations required for that plugin, so installing it manually should just involve checking it out in your plugins folder and precompiling the assets.

(Jeff Atwood) #7

Non-Docker installs are not supported here.

We have limited staff and time, and we regret that we cannot support non-standard installs.

(Tuan Anh Tran) #8

I have this issue as well. Have you found a workaround?


The solution is simple.

git pull
cd plugins
git clone  [link to plugins]
cd ..
rake db:migrate
rake assets:precompile RAILS_ENV=production

Something like that.

Install a Plugin
(Tuan Anh Tran) #10

I did that. Didn’t work for me.

The plugins do not show up in plugins admin page.

stdout from db:migrate and precompile asset look good to me.

These are the content of plugins folder

discourse-akismet  discourse-spoiler-alert  discourse-tagging  lazyYT  poll

Only lazyYT and poll is shown up in plugins admin.


Did you:

git pull

To download the latest discourse?

Go to /admin/upgrade and see if there is updates

You may need to check ownership/permission differences

Go to plugins folder in terminal and:

ls -la

Do you see different ownership from the ones showing and the newly created?

(Tuan Anh Tran) #12

I’m on 1.4.6; and admin/upgrade returns 404 for me.

ls -ls return the same ownership (drwxr-xr-x) as with the other 2 plugins that successfully installed.


Something is amiss, here is what admin/upgrade returns for me:

When did you initially deploy discourse? I’m wondering if you are using some components which have been obsoleted. You try the page after logging in as an admin? I will see a server 500 if not logged in.

(Tuan Anh Tran) #14

I installed Discourse few days back.

i got that screen as well when i was using Docker.

(Tuan Anh Tran) #15

Ah I just figure it out i have to reload unicorn as well.