[Archivesspace_Users_Group] Plugin gems

Mayo, Dave dave_mayo at harvard.edu
Mon Mar 14 12:04:19 EDT 2016

ArchivesSpace manages gems using bundler - and kind of a complicated bundler setup.

The best solution is, as far as I understand it, to put the gemfiles in the appropriate place in the plugin, and then run bundler against the relevant gemfile/gemfiles.

There's a build/run task called bundler, which would be run something like this:

./build/run bundler -Dgemfile=backend/Gemfile

- Dave

From:  <Flanagan>, Patrick <PJFlanagan at ship.edu<mailto:PJFlanagan at ship.edu>>
Reply-To:  Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Date:  Monday, March 14, 2016 at 10:09 AM
To:  "archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>" <archivesspace_users_group at lyralists.lyrasis.org<mailto:archivesspace_users_group at lyralists.lyrasis.org>>
Subject:  [Archivesspace_Users_Group] Plugin gems

Good morning,
I'm not exceedingly familiar with rails development. I'm making what should be a simple plugin, but I need a gem installed for it to work.
gem install works on the OS side, but when ArchivesSpace gets to my plugin, it doesn't find the gem with
require. What is the process of making ArchivesSpace aware of new gems for plugins? (Or rather, what is the correct way to do it?) This is for version 1.4.2.
Thank you for your time,
~Patrick Flanagan
KLN Applications Administrator
Keystone Library Network Hub
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160314/b15c05f9/attachment.html>

More information about the Archivesspace_Users_Group mailing list