Changes between Initial Version and Version 3 of Ticket #441


Ignore:
Timestamp:
10/26/10 11:00:21 (4 years ago)
Author:
dread
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #441 – Description

    initial v3  
    11When performing maintenance on CKAN it may be necessary to make CKAN obviously read-only, telling the users and restricting access to 'edit' pages. 
    22 
    3 Example of maintenance would be switching between two parallel CKAN instances - you want to make it RO when you do the backup and until you bring up the new one. 
     3Examples of use: 
     4 * 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. 
     5 * A CKAN is used just for distributing metadata and so is always read-only. Updates may still arrive through direct db manipulation, e.g.: 
     6   * another (but writable) CKAN instance is connected to the same db 
     7   * restoring database dumps from another CKAN db 
     8 * Should a security be breached, all editing could be stopped 
    49 
    5 This would also be useful for the public DGU read-only CKAN. 
    6  
    7 It would also be useful for a fail-over CKAN server that is only used in the event of problems, and no edits will be transferred back to the main server.