<div dir="ltr"><div><div><div><div>Chris,<br><br></div>Thanks! We'll definitely try that out to keep our code up-to-date.<br><br></div>What we aren't clear on is the best method of turning our fork of <a href="https://github.com/archivesspace/archivesspace">https://github.com/archivesspace/archivesspace</a> into something deployable. Should we fork the repository, commit to the fork, run the build system, and deploy the build? Or would it be wiser to fork the repository, commit to the fork, then copy any new code to a plugins repository (which then gets deployed)?<br><br></div><div>Regarding plugins - is there any real limitation as to how far plugins can go before we would need to start rolling our own builds?<br></div><div><br></div>Thanks,<br></div>--Alex<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 11, 2016 at 3:29 PM, Chris Fitzpatrick <span dir="ltr"><<a href="mailto:Chris.Fitzpatrick@lyrasis.org" target="_blank">Chris.Fitzpatrick@lyrasis.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-size:12pt;color:#000000;background-color:#ffffff;font-family:Calibri,Arial,Helvetica,sans-serif">
<br>
<p>Hi,</p>
<p><br>
</p>
<p>One thing you can do is to just set and upstream repo in git. I.e. : <br>
</p>
<p><br>
</p>
<p>0 ) Fork the main archivesspace/archivesspace repo and clone it</p>
<p>1 ) Add an upstream remote to your clone ( git remote add upstream <a title="Cmd+Click or tap to follow the link" href="https://github.com/archivesspace/archivesspace.git" target="_blank">
https://github.com/archivesspace/archivesspace.git</a> ) <br>
</p>
<p>2 ) now you can pull down any upstream changes ( git pull upstream master, or make a branch first, pull the upstream into that branch, then merge the brance into your master )
<br>
</p>
<p><br>
</p>
<p>Does that make sense? <br>
</p>
<p>b,chris. <br>
</p>
<p><br>
</p>
<p><br>
</p>
<div>
<div name="divtagdefaultwrapper">
<div><font size="2">
<div>Chris Fitzpatrick | <font size="2">Developer, ArchivesSpace</font><br>
Skype: chrisfitzpat | Phone: <a href="tel:918.236.6048" value="+19182366048" target="_blank">918.236.6048</a><br>
<a href="http://archivesspace.org/" target="_blank">http://archivesspace.org/</a><br>
</div>
</font></div>
</div>
</div>
<br>
<br>
<div style="color:rgb(0,0,0)">
<hr style="display:inline-block;width:98%">
<div dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org" target="_blank">archivesspace_users_group-bounces@lyralists.lyrasis.org</a>> on behalf of Alexander Duryee
<<a href="mailto:alexanderduryee@nypl.org" target="_blank">alexanderduryee@nypl.org</a>><br>
<b>Sent:</b> Friday, March 11, 2016 8:08 PM<br>
<b>To:</b> Archivesspace Users Group<span class=""><br>
<b>Subject:</b> [Archivesspace_Users_Group] ArchivesSpace codebase repository setup</span></font>
<div> </div>
</div><div><div class="h5">
<div>
<div dir="ltr">
<div>
<div>
<div>
<div>
<div>
<div>
<div>We're undertaking local feature development for ArchivesSpace (ranging from EAD/MARC export tweaking to database migrations and corresponding UI updates); as such, we're setting up code repositories for our local codebase. Given that the ASpace application
doesn't map cleanly to the source repo, it's not immediately clear what the best setup for a code repository will be.<br>
<br>
</div>
How has the list set up their local code repositories? Right now, there seem to be a few options for us:<br>
<br>
</div>
- fork the main ASpace repository, work there, and deploy a full copy of the repo into /plugins/local/ (losing migration/config source control)<br>
</div>
- set up a repo that contains the ASpace application, work in plugins/ (and migrations/ and config/ when needed), and deploy the entire application at once<br>
</div>
- set up a repo of just /plugins/, work there, and deploy that (losing config/migration source control)<br>
<br>
</div>
We're leaning towards the second option (if only to keep configs/migrations under source control), but none of these implementations feels satisfactory. Are there other methods of maintaining source control for ArchivesSpace code/config that the list is using?<br>
<br>
</div>
Thanks,<br>
</div>
--Alex<br clear="all">
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div><br>
-- <br>
<div>
<div dir="ltr">
<div>
<div dir="ltr">Alexander Duryee
<div>Metadata Archivist</div>
<div>New York Public Library</div>
<div><a href="tel:%28917%29-229-9590" value="+19172299590" target="_blank">(917)-229-9590</a></div>
<div><a href="mailto:alexanderduryee@nypl.org" target="_blank">alexanderduryee@nypl.org</a></div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div></div></div>
</div>
</div>
<br>_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr">Alexander Duryee<div>Metadata Archivist</div><div>New York Public Library</div><div>(917)-229-9590</div><div><a href="mailto:alexanderduryee@nypl.org" target="_blank">alexanderduryee@nypl.org</a></div></div></div></div></div>
</div>