<div dir="ltr">Presently, we use SVN to manage the deployment. We have two repositories. One for configs which the IdP loads on startup via the Subversion resource [1], and one for the distribution & dependencies. It's not ideal, but it does work. We are looking to move off of this setup and onto one that uses versioned Docker images + Git to manage the image build+config changes. <div><br></div><div>Dave</div><div><br></div><div>[1] <a href="https://wiki.shibboleth.net/confluence/display/SHIB2/IdPConfigResource">https://wiki.shibboleth.net/confluence/display/SHIB2/IdPConfigResource</a></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 3, 2015 at 11:56 AM, Benjamin Cherian <span dir="ltr"><<a href="mailto:benjamin.cherian@villanova.edu" target="_blank">benjamin.cherian@villanova.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">For those that have been using IdP for a while, what solution(s) are you<br>
using to manage instances of IdP and changed made to the configuration. Do<br>
you use a VCS like Git or SVN, or another tool like Chef or Ansible? What<br>
does your setup look like how does your deployment process look like?<br>
<br>
Currently we're looking to setup a load balanced solution with 2 IdP<br>
servers in both dev and production. We want a solid solution for managing<br>
when we add new RPs, change attribute filters, and make other<br>
configuration changes.<br>
<br>
Thanks,<br>
Ben Cherian<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">David Langenberg<div>Identity & Access Management</div><div>The University of Chicago</div></div>
</div>