CMS maintenance checklist
Permalink
we need some assurances on general CMS maintenance and wanted to tap into the forum to try and establish a list of common housekeeping/maintenance processes that would be required to keep a CMS/Concrete5 site healthy. For contingency purposes we want almost a how to go/checklist that another officer could pick up if a core admin was unavailable for a period of time. There are obvious things like how to check for updates/patches and how to apply which should be documented, but a more detailed list of day to day ops that a CMS/Concrete5 admin has to do to stay on top of things would be most helpful and interesting.
This sounds like an excellent idea. I'd definitely suggest creating new backups (files and database) in accordance with whatever your policy is (and, at very minimum, before any upgrade or non-trivial site edit).
You could also look periodically at error logs (c5, php, server), and keep an eye on server resource usage (CPU, memory, bandwidth).
You could also look periodically at error logs (c5, php, server), and keep an eye on server resource usage (CPU, memory, bandwidth).
If we are talking about future plans then you need to post it in another part of the forum, not here which is for deprecated versions of C5.
If on the other hand you already have a C5 website, can you tell us what version it is?