http://localhost/ticket/441 <p> When performing maintenance on CKAN it may be necessary to make CKAN obviously read-only, telling the users and restricting access to 'edit' pages. </p> <p> Examples of use: </p> <ul><li>Administrator wants to upgrade CKAN or move it to another server. During this time the database is being administered and either edits are lost or can't be done. </li><li>A CKAN is used just for distributing metadata and so is always read-only. Updates may still arrive through direct db manipulation, e.g.: <ul><li>another (but writable) CKAN instance is connected to the same db </li><li>restoring database dumps from another CKAN db </li></ul></li><li>Should a security be breached, all editing could be stopped </li></ul> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/441 Trac 0.12.3 dread Wed, 25 Aug 2010 08:21:49 GMT http://localhost/ticket/441#comment:1 http://localhost/ticket/441#comment:1 <p> Comment from pudo: Apache version is documented here: <a class="ext-link" href="http://knowledgeforge.net/okfn/tasks/ticket/466"><span class="icon">​</span>http://knowledgeforge.net/okfn/tasks/ticket/466</a> </p> Ticket anonymous Wed, 25 Aug 2010 08:23:05 GMT http://localhost/ticket/441#comment:2 http://localhost/ticket/441#comment:2 <p> Comment from pudo: CKAN should have a read-only maintenance mode with a nice little banner on all pages, appropriate REST messages etc. Bonus points if this is triggered via an environment variable and thus can be triggered by the surrounding apache. </p> Ticket dread Tue, 26 Oct 2010 11:00:21 GMT http://localhost/ticket/441#comment:3 http://localhost/ticket/441#comment:3 <ul> <li><strong>description</strong> modified (<a href="/ticket/441?action=diff&amp;version=3">diff</a>) </li> </ul> Ticket dread Mon, 01 Nov 2010 10:21:58 GMT http://localhost/ticket/441#comment:4 http://localhost/ticket/441#comment:4 <ul> <li><strong>owner</strong> set to <em>dread</em> </li> </ul> Ticket johnbywater Mon, 15 Nov 2010 10:10:47 GMT http://localhost/ticket/441#comment:5 http://localhost/ticket/441#comment:5 <ul> <li><strong>summary</strong> changed from <em>Read-only state for CKAN</em> to <em>CKAN shall support being put into read-only state</em> </li> </ul> Ticket johnbywater Mon, 15 Nov 2010 10:11:40 GMT http://localhost/ticket/441#comment:6 http://localhost/ticket/441#comment:6 <ul> <li><strong>summary</strong> changed from <em>CKAN shall support being put into read-only state</em> to <em>The system shall support being put into read-only state</em> </li> </ul> Ticket dread Mon, 15 Nov 2010 12:04:42 GMT http://localhost/ticket/441#comment:7 http://localhost/ticket/441#comment:7 <ul> <li><strong>summary</strong> changed from <em>The system shall support being put into read-only state</em> to <em>CKAN read-only state</em> </li> </ul> Ticket dread Fri, 17 Dec 2010 11:45:09 GMT http://localhost/ticket/441#comment:8 http://localhost/ticket/441#comment:8 <ul> <li><strong>priority</strong> set to <em>awaiting triage</em> </li> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>duplicate</em> </li> </ul> <p> No need for requirements. Story tickets exist: <a class="assigned ticket" href="http://localhost/ticket/763" title="enhancement: Read-only mode - Setup (assigned)">#763</a> &amp; <a class="assigned ticket" href="http://localhost/ticket/765" title="enhancement: Read-only mode - API usage (assigned)">#765</a> </p> Ticket