http://localhost/ticket/1165 <p> Currently, each ckan site needs its own ckan wsgi process. That eats a lot of resources where many ckan sites are served from one machine (e.g. eu3). </p> <p> That would dramatically change if a ckan process could behave like multiple ckans (e.g. like Apache's "&lt;<a class="missing wiki">VirtualHost?</a>&gt;", or tracd). Depending on the "Host:" header in the HTTP1.1 request, it would choose which local ckan ini file to obey. </p> <p> I see two ways to constitute the map hostname-to-ini-file map: </p> <ul><li>ckan reads a set of ini files, and each ini file declares which servers names it is responsible for </li><li>In a global ini file, there are directives mapping servernames to ini files. </li></ul><p> In either case there should be a global ckan ini having the default settings for all local ckan sites. Each site ini could be very short then, just having e.g. title, name, database credentials, active plugins etc. </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/1165 Trac 0.12.3 nils.toedtmann Thu, 26 May 2011 12:45:53 GMT http://localhost/ticket/1165#comment:1 http://localhost/ticket/1165#comment:1 <p> this is similar, but not equal to <a class="new ticket" href="http://localhost/ticket/1096" title="defect: [super] CKAN Hosted (new)">#1096</a> </p> Ticket nils.toedtmann Tue, 07 Jun 2011 11:05:33 GMT http://localhost/ticket/1165#comment:2 http://localhost/ticket/1165#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 seanh Fri, 15 Jun 2012 15:34:26 GMT http://localhost/ticket/1165#comment:3 http://localhost/ticket/1165#comment:3 <ul> <li><strong>keywords</strong> <em>deployment</em> added </li> <li><strong>milestone</strong> set to <em>ckan-future</em> </li> </ul> Ticket