Ticket #2469 (closed enhancement: duplicate)

Opened 2 years ago

Last modified 23 months ago

Find a better way to deploy CKAN instances

Reported by: seanh Owned by: seanh
Priority: awaiting triage Milestone: ckanbuild
Component: ckan Keywords: deployment
Cc: Repository: ckan
Theme: none


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.

Components that this might include:

Virtualenv bootstrap script https://gist.github.com/2206132

Ansible http://ansible.github.com/

CKAN deb package

Change History

comment:1 Changed 23 months ago by seanh

  • Owner changed from kindly to seanh
  • Status changed from new to assigned
  • Milestone changed from current-ckan-sprint-2012-06-25 to ckanbuild

comment:2 Changed 23 months ago by seanh

  • Keywords deployment added

comment:3 Changed 23 months ago by seanh

  • Status changed from assigned to closed
  • Resolution set to duplicate

Closing this, has been broken down into individual tickets, see ckanbuild milestone

Note: See TracTickets for help on using tickets.