http://localhost/ticket/2469 <p> We want a much quicker and easier way of deploying multiple CKAN instances to the same or multiple servers and managing them (e.g. configuration, themes, extensions, upgrades, and adding new instances). Currently we just deploy and manage each instance separately, which doesn't scale.. We'd also want to have (as far as possible) one single way of deploying CKAN that works across different situations, e.g. deployment server, demo server, jenkins, local deployment for development, these should share the same tools for installing CKAN and its dependencies. </p> <p> Components that this might include: </p> <p> Virtualenv bootstrap script <a class="ext-link" href="https://gist.github.com/2206132"><span class="icon">​</span>https://gist.github.com/2206132</a> </p> <p> Ansible <a class="ext-link" href="http://ansible.github.com/"><span class="icon">​</span>http://ansible.github.com/</a> </p> <p> CKAN deb package </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/2469 Trac 0.12.3 seanh Fri, 15 Jun 2012 16:16:32 GMT http://localhost/ticket/2469#comment:1 http://localhost/ticket/2469#comment:1 <ul> <li><strong>owner</strong> changed from <em>kindly</em> to <em>seanh</em> </li> <li><strong>status</strong> changed from <em>new</em> to <em>assigned</em> </li> <li><strong>milestone</strong> changed from <em>current-ckan-sprint-2012-06-25</em> to <em>ckanbuild</em> </li> </ul> Ticket seanh Mon, 18 Jun 2012 15:43:13 GMT http://localhost/ticket/2469#comment:2 http://localhost/ticket/2469#comment:2 <ul> <li><strong>keywords</strong> <em>deployment</em> added </li> </ul> Ticket seanh Mon, 25 Jun 2012 15:55:02 GMT http://localhost/ticket/2469#comment:3 http://localhost/ticket/2469#comment:3 <ul> <li><strong>status</strong> changed from <em>assigned</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>duplicate</em> </li> </ul> <p> Closing this, has been broken down into individual tickets, see ckanbuild milestone </p> Ticket