Specifying the gem dependecies for plugin - gem does not exist

[net_deamon]

I did go through the suggesstions in following posts

Plugin using own gem

Gems declared in a plugin are installed and loaded differently as per our implementation: In order to get it to work, you’ll have to specify all the gem’s dependencies which are not already included in the Gemfile.

Newrelic plugin

New Relic support Author: Sam Saffron Support for http://newrelic.com plugins/newrelic/plugin.rb # name: enable New Relic rpm # about: New Relic support # version: 0.1 # authors: Sam Saffron ENV["NRCONFIG"] = File.expand_path('../newrelic.yml', __FILE__) gem "newrelic_rpm", "3.6.7.152" NewRelic::Control.instance.init_plugin :config => Rails.configuration after_initialize do ForumsController.newrelic_ignore :only => [:status] end plugins/newrelic/newrelic.yml The file you got from newrel…

So I tried 2 ways

Specifying in plugin.rb file

---

My plugin depends upon “mini_magick” for image resizing, so I specified it in plugin.rb

gem ‘mini_magick’, ‘~> 4.8’

But I get the following error

I, [2017-07-09T03:54:49.899941 #13] INFO – : > cd /var/www/discourse && sudo -E -u discourse bundle exec rake db:migrate
ERROR: While executing gem … (Gem::Requirement::BadRequirementError)
Illformed requirement ["/root"]
I, [2017-07-09T03:54:54.692893 #13] INFO – : /root is not writable.
Bundler will use `/tmp/bundler/home/discourse’ as your home directory temporarily.
gem install mini_magick -v ~> 4.8 -i /var/www/discourse/plugins/discussbook-plugin/gems/2.4.1 --no-document --ignore-dependencies
You are specifying the gem mini_magick in /var/www/discourse/plugins/discussbook-plugin/plugin.rb, however it does not exist!

Specifying in yml file

---

As it was not working, I tried to add the gem install command in yml file custom commands

• exec: gem install mini_magick -v 4.8.0

I get the following log(success) when it was being rebuilt

I, [2017-07-08T18:50:43.302333 #13] INFO – : Beginning of custom commands
I, [2017-07-08T18:50:43.302751 #13] INFO – : > gem install mini_magick -v 4.8.0
I, [2017-07-08T18:50:44.034391 #13] INFO – : Successfully installed mini_magick-4.8.0
1 gem installed

But when I try to require it in the route, I got the following error in error log

NameError (uninitialized constant) DiscussBook::DiscussbookController::MiniMagick)

Both of these trials did not work, can you please help me regarding what might be the error?

[pfaffman]

I don’t know, but you might make sure that the directory that is getting to write to is world writable.

[net_deamon]

I can run the plugin locally… But in the server, the docker rebuild causes this issue.
Are you suggesting that I should enter inside docker, and change the permissions of folder to writable?
I will try that out, but if it would have been possible from plugin itself, it would be great.

[sam]

This is not how you include gems,

Plugin with custom gems

Add your gem dependencies (all the dependency tree) to your plugin.rb file:

The version has to be specific, you can not use ~>

[pfaffman]

Apparently, the most salient part of my earlier message was “I don’t know”.

[net_deamon]

Hi @sam, thanks for answer.
I tried this many times in different configurations, but it failed. Then I came to know real cause, though I do not know the solution

When I install the discourse-backups-to-dropbox plugin from github (plugin that you shared), the docker builds properly. But if I put it discourse-backups-to-dropbox in private repository like bitbucket, it throws the error. The error logs for the plugin are same as shared in first post ie

E -u discourse bundle exec rake db:migrate
ERROR: While executing gem … (Errno::EACCES)
Permission denied @ dir_s_mkdir - /var/www/discourse/plugins/discourse-backups-to-dropbox/gems
I, [2017-07-10T18:18:41.229582 #15] INFO – : /root is not writable.
Bundler will use `/tmp/bundler/home/discourse’ as your home directory temporarily.
gem install public_suffix -v 2.0.5 -i /var/www/discourse/plugins/discourse-backups-to-dropbox/gems/2.4.1 --no-document --ignore-dependencies
You are specifying the gem public_suffix in /var/www/discourse/plugins/discourse-backups-to-dropbox/plugin.rb, however it does not exist!
I, [2017-07-10T18:18:41.230126 #15] INFO – : Terminating async processes

So I guess the problem lies in the my private repo configuration. But if the plugin(without any gem) gets installed properly from bitbucket, I do not know why would installing plugin with gem throw error. It should not matter whether the plugin is in open repository like github or in private repo like bitbucket.

My private repo config

• exec: cd /var/www/discourse && sudo -u discourse bundle install --deployment --without test --without development
• exec: mkdir /root/.ssh
• exec: ssh-keyscan -t rsa bitbucket.org > /root/.ssh/known_hosts
• exec: echo “Host bitbucket\n\tStrictHostKeyChecking no\n\tHostName bitbucket.com\n\tIdentityFile /root/.ssh/id_rsa\n” >> /root/.ssh/config
• file:
  path: /root/.ssh/id_rsa
  chmod: 600
  contents: |
  -----BEGIN RSA PRIVATE KEY-----
  …
  …
  -----END RSA PRIVATE KEY-----
• file:
  path: /root/.ssh/id_rsa.pub
  chmod: 600
  contents: ssh-rsa …
• exec: cd $home/plugins && git clone git@bitbucket.org:path/to/discourse-backups-to-dropbox.git
• exec: cd $home && sudo -E -u discourse bundle exec rake db:migrate
• exec: cd $home && rm -fr tmp/cache
• exec: cd $home && sudo -E -u discourse bundle exec rake assets:precompile
• exec: rm /root/.ssh/id_rsa
• exec: rm /root/.ssh/id_rsa.pub

Its same as mentioned in tutorial

Install a Plugin

To add a private git repository plugin, you need to follow these steps: Assuming that your private git repo is hosted on GitHub, you need to add your server’s user public SSH key to GitHub repo Deploy keys (https://github.com/SecretOrg/secret-plugin/settings/keys). Modify app.yml file as shown in below example: run: - exec: echo “Beginning of custom commands” - exec: cd /var/www/discourse && sudo -u discourse bundle install --deployment --without test --without development - ex…

[pfaffman]

I still don’t know.

If sounds like a permissions problem. You might chmod - r 777 the repo after you clone it.

[net_deamon]

You are awesome @pfaffman. Thanks

[RGJ]

chmod - r 777

That is one hell of a scary advice.
I advise to figure out which user needs write permissions, and then chown it to that user, keeping the permissions at 0755.

[net_deamon]

Thanks ,
Yes I am now rebuilding with 755.
Atleast I got to know where the issue was.
I had been struggling with this for 3 days …

[pfaffman]

Yes. Once you see if that fixes it and what the ownership of the files created are, you should take steps to lock things back down.