<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p><br>
</p>
<p><br>
</p>
<p>Hi,</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>If you just want to develop against a packaged version of ArchivesSpace, you can just use the scripts/initialize_plugins.sh <plugin name> script and it will install your gems.
<br>
</p>
<p><br>
</p>
<p>Also, FYI and loop-back to something I talked with some folks at C4L<a title="Cmd+Click or tap to follow the link" href="https://github.com/archivesspace/archivesspace/commit/11a55481a970d02f9ba5691577848550538ebbb6">, I just updated the initialize_plugins.sh
script</a> to unset the GEM_HOME and GEM_PATH variables, which was causing problems with the Redis demo plugin I did ( a problem if you're using something like RVM or Chruby ).
<br>
</p>
<p>I think that should fix it...no need to do a new update, you can just add those two UNSET lines to an existing script.
</p>
<p><br>
</p>
<p>b,chris. <br>
</p>
<p><br>
<br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<div id="Signature">
<div name="divtagdefaultwrapper" style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:; margin:0">
<div class="BodyFragment"><font size="2">
<div class="PlainText">Chris Fitzpatrick | <font size="2">Developer, ArchivesSpace</font><br>
Skype: chrisfitzpat | Phone: 918.236.6048<br>
http://archivesspace.org/<br>
</div>
</font></div>
</div>
</div>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" color="#000000" face="Calibri, sans-serif"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Mayo, Dave
<dave_mayo@harvard.edu><br>
<b>Sent:</b> Monday, March 14, 2016 5:04 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] Plugin gems</font>
<div> </div>
</div>
<div>
<div>ArchivesSpace manages gems using bundler - and kind of a complicated bundler setup.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>There's a build/run task called bundler, which would be run something like this:</div>
<div><br>
</div>
<div>./build/run bundler -Dgemfile=backend/Gemfile</div>
<div><br>
</div>
<div>- Dave</div>
<div><br>
</div>
<div>From: <Flanagan>, Patrick <<a href="mailto:PJFlanagan@ship.edu">PJFlanagan@ship.edu</a>></div>
<div>Reply-To: Archivesspace Users Group <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>></div>
<div>Date: Monday, March 14, 2016 at 10:09 AM</div>
<div>To: "<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>" <<a href="mailto:archivesspace_users_group@lyralists.lyrasis.org">archivesspace_users_group@lyralists.lyrasis.org</a>></div>
<div>Subject: [Archivesspace_Users_Group] Plugin gems</div>
<div><br>
</div>
<div><br>
</div>
<div>Good morning,</div>
<div></div>
<div>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.</div>
<div>gem install works on the OS side, but when ArchivesSpace gets to my plugin, it doesn’t find the gem with</div>
<div>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.</div>
<div></div>
<div>Thank you for your time,</div>
<div></div>
<div>~Patrick Flanagan</div>
<div>KLN Applications Administrator</div>
<div>Keystone Library Network Hub</div>
</div>
</div>
</div>
</body>
</html>