Ticket #441 (closed requirement: duplicate)
CKAN read-only state
| Reported by: | dread | Owned by: | dread |
|---|---|---|---|
| Priority: | awaiting triage | Milestone: | ckan-v1.3 |
| Component: | ckan | Keywords: | |
| Cc: | Repository: | ||
| Theme: |
Description (last modified by dread) (diff)
When performing maintenance on CKAN it may be necessary to make CKAN obviously read-only, telling the users and restricting access to 'edit' pages.
Examples of use:
- 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.
- A CKAN is used just for distributing metadata and so is always read-only. Updates may still arrive through direct db manipulation, e.g.:
- another (but writable) CKAN instance is connected to the same db
- restoring database dumps from another CKAN db
- Should a security be breached, all editing could be stopped
Change History
comment:2 Changed 4 years ago by anonymous
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.
comment:5 Changed 3 years ago by johnbywater
- Summary changed from Read-only state for CKAN to CKAN shall support being put into read-only state
comment:6 Changed 3 years ago by johnbywater
- Summary changed from CKAN shall support being put into read-only state to The system shall support being put into read-only state
Note: See
TracTickets for help on using
tickets.
Comment from pudo: Apache version is documented here: http://knowledgeforge.net/okfn/tasks/ticket/466