Having a highly used systems we need to rethink our policy to replace live files on disk. Under no circumstance we should remove/rename any file while in use. This breaks various parts of the system from not being able to render notification templates to user visible errors if a NavPage template is missing.
The most common process we have adopted so far was to rename the old file as a backup and drop in the new file. However, there is a small time window in which we don't have any file the system could use during the replacement.
To eliminate that time window I have the following suggestion to replace files on live systems:
- Copy any file which will be replaced and rename the copy of the file for backup purposes
- Overwrite the original file with the new version
All files in the system are affected (incl. course content). However, template files in particular are critical because they have quite some affect on the system. For example, if a certificate template can't be rendered, we may not re-try and would loose a certificate for a user.
Template files include
- Certificate template
- Notification template
- NavPage templates and any referenced file like js or css.
Related articles
Filter by label
There are no items with the selected labels at this time.
Add Comment