If Calpendo is installed on your own servers, it may be necessary to create a backup instance that runs against a copy of the database. Normally such a copy would want to be configured to be read-only so that people can connect to it to access information, but cannot change anything.
There are three ways to place your Calpendo into a read-only mode:
1.Set up the access rights for the database user so that it does not have insert Permission to the exprodo_events table. A system event is created at boot time, and if the insert fails, this is used as a trigger to assume a read-only mode.
2.Set the read-only mode setting in the Global Preferences' General tab.
3.Change the read-only mode by directly modifying the database. Here is an example of the SQL you would use if you are using MySQL to store the Calpendo database:
4.
update config_properties set boolval='T' where name='readOnlyMode'; |
To manually modify the database to disable read-only mode that is trigged by setting the global preferences, run this SQL:
update config_properties set boolval='F' where name='readOnlyMode'; |
Requirements For A Read-Only Database
If you create a database and configure Calpendo's database user so that it has no insert or update Permissions, then Calpendo will not work properly. To make it work, you must at least have the following Permissions (this is expressed in MySQL code):
GRANT SELECT ON `calpendo`.* TO 'calpendo_ro'@'localhost' identified by 'thepassword'; |
where calpendo_ro is the name of the database user.
Consequences of Putting Calpendo Into Read-Only Mode
In read-only mode, the following apply:
•Reminders emails are disabled. This is because Calpendo cannot track which reminders have or have not been sent.
•Automatic Emails do not run
•When using the Bookings Calendar, it does not offer the ability to edit anything
•Normally, when a repeat booking or repeat Time Template passes a due time, a new instance of the booking or Time Template is created so that Calpendo keeps a record of what bookings or Time Templates were in effect. It means that all past records should be accurate. In read-only mode, no such modification takes place. This means that the record of the past is not the same as it would be for a read-write Calpendo.