http://localhost/ticket/1096 <p> Many users of CKAN want to have their own instance without much effort. Setting these up in separate places is a maintenance nightmare, we should much rather have some tenant separation in core CKAN. Some ideas: </p> <ul><li>introduce model.Site and c.site <ul><li>site has: custom CSS, extra_template_path, title, languages list, package_form, group_form (all configured via web UI) </li></ul></li><li>Subdomain detector to activate sites. </li><li>use site in Authorizer instead of System, have a <a class="missing wiki">NullSite?</a> for global things </li><li>allow cross-site search </li><li>packages are in a list of sites, m:n rather than 1:n <ul><li>list of sites is string-based, can contain sites not in site table to express harvested external material which is not editable locally. </li></ul></li></ul> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/1096 Trac 0.12.3 pudo Tue, 19 Apr 2011 17:44:43 GMT http://localhost/ticket/1096#comment:1 http://localhost/ticket/1096#comment:1 <ul> <li><strong>description</strong> modified (<a href="/ticket/1096?action=diff&amp;version=1">diff</a>) </li> </ul> Ticket nils.toedtmann Tue, 07 Jun 2011 11:03:46 GMT http://localhost/ticket/1096#comment:2 http://localhost/ticket/1096#comment:2 <p> See also <a class="ext-link" href="http://ckan.okfnpad.org/multisite"><span class="icon">​</span>http://ckan.okfnpad.org/multisite</a> </p> Ticket thejimmyg Fri, 08 Jul 2011 11:39:33 GMT http://localhost/ticket/1096#comment:3 http://localhost/ticket/1096#comment:3 <ul> <li><strong>summary</strong> changed from <em>Introduce Site domain object for subdomain tenants</em> to <em>CKAN Hosted</em> </li> </ul> <p> Renaming to CKAN Hosted because whether we introduce a site domain object for subdomain tenants or not is an implementation detail. </p> <p> As far as progress on CKAN hosted goes, we now have: </p> <ul><li>A build tool to package ckanext-dgu, ckanext-std etc into .deb files </li><li>The ability to apt-get install CKAN </li><li>A script that can set up multiple non-conflicting CKAN instances on the same machine </li></ul><p> What we need next is the ability to generate a ckanext-xxx repository for each new instance we want to host. At that point most of the underlying techniques for hosting multiple CKAN instances concurrently will be in place. Once we have that working and know what clients want, we can look at going further and speccing up a multisite solution off a single DB, rather than the multi-instance solution proposed here. </p> Ticket thejimmyg Wed, 20 Jul 2011 17:16:48 GMT http://localhost/ticket/1096#comment:4 http://localhost/ticket/1096#comment:4 <ul> <li><strong>summary</strong> changed from <em>CKAN Hosted</em> to <em>[super] CKAN Hosted</em> </li> <li><strong>milestone</strong> changed from <em>ckan-backlog</em> to <em>ckan-v-future</em> </li> </ul> Ticket thejimmyg Wed, 20 Jul 2011 17:17:42 GMT http://localhost/ticket/1096#comment:5 http://localhost/ticket/1096#comment:5 <ul> <li><strong>milestone</strong> <em>ckan-v-future</em> deleted </li> </ul> <p> Milestone ckan-v-future deleted </p> Ticket thejimmyg Wed, 20 Jul 2011 17:18:51 GMT http://localhost/ticket/1096#comment:6 http://localhost/ticket/1096#comment:6 <ul> <li><strong>milestone</strong> set to <em>ckan-future</em> </li> </ul> Ticket seanh Fri, 15 Jun 2012 15:34:44 GMT http://localhost/ticket/1096#comment:7 http://localhost/ticket/1096#comment:7 <ul> <li><strong>keywords</strong> <em>deployment</em> added </li> </ul> Ticket