Deactivating a live Ketida instance
Feature proposal: [Deactivating a live Ketida instance] Context
De Active Ketida Instance
Currently, there is no option to deactivate an existing Ketida instance. One of our customers is planning to use multiple Ketida instances for various publishers and they want to have an option to deactivate a particular instance and activate it later if required.
Proposal
Whenever we receive a request to deactivate a particular Ketida instance, the following features must be disabled for usage. Users could log in to the said Ketida instance with a read-only view. However, they can download the files from the existing books.
Following features / functionality must be disabled;
Add new book, Upload files, Upload Assets, Assign team members, Edit the content, Readonly Wax Editor, Rename, Archive, Add Metadata, Add Templates, Edit Templates
All features must be reverted once we make the instance active again.
Design
Sample 1
Sample 2
Implementation (if applicable)
Create a script that can be run from CLI of the server to deactivate/activate a Ketida instance.
Alternative approaches (if applicable)
None
Open issues (if applicable) None