<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>Hi Chris and Alex,</p>
<p><br>
</p>
<p>I'm interested in this discussion and the set-up others are using, as I'm not sure that the set-up we have for ArchivesSpace development is ideal.</p>
<p><br>
</p>
<p>We are also customising ArchivesSpace and have made tweaks to the EAD import, footer, import jobs page. We have forked ArchivesSpace into a UoEMainLibrary GitHub account, which we then fork into our own accounts for doing development and then clone. This
means that we make pull requests to the team account for changes. We have also created branches prefixed with uoe that are copies of the corresponding ArchivesSpace release tag. As I would rather than we only released the latest release from ArchivesSpace
with our changes and not the master. We then deploy the whole application at once from this branch.</p>
<p><br>
</p>
<p>Thanks,<br>
</p>
<p><br>
</p>
<p>Claire<br>
</p>
<p><br>
</p>
<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" face="Calibri, sans-serif" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Chris Fitzpatrick
<Chris.Fitzpatrick@lyrasis.org><br>
<b>Sent:</b> 11 March 2016 20:29<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> Re: [Archivesspace_Users_Group] ArchivesSpace codebase repository setup</font>
<div> </div>
</div>
<div>
<div id="divtagdefaultwrapper" 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" id="LPlnk410351" href="https://github.com/archivesspace/archivesspace.git">
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 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" face="Calibri, sans-serif" color="#000000"><b>From:</b> archivesspace_users_group-bounces@lyralists.lyrasis.org <archivesspace_users_group-bounces@lyralists.lyrasis.org> on behalf of Alexander Duryee
<alexanderduryee@nypl.org><br>
<b>Sent:</b> Friday, March 11, 2016 8:08 PM<br>
<b>To:</b> Archivesspace Users Group<br>
<b>Subject:</b> [Archivesspace_Users_Group] ArchivesSpace codebase repository setup</font>
<div> </div>
</div>
<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 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>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>