Nazar Gargol 5582d030e3 Added routes.yaml content checksum storage to the db ... closes #11999 - When the routes.yaml file changes (manually or through API) we need to store a checksum to be able to optimize routes reloads in the future - Added mechanism to detect differences between stored and current routes.yaml hash value - Added routes.yaml sync on server boot - Added routes.yaml handling in controllers - Added routes hash synchronization method in core settings. It lives in core settings as it needs access to model layer. To avoid coupling with the frontend settings it accepts a function which has to resolve to a routes hash - Added note about settings validation side-effect. It mutates input! - Added async check for currently loaded routes hash - Extended frontend settings loader with async loader. The default behavior of the loader is to load settings syncronously for reasons spelled in 0ac19dcf84 To avoid blocking the eventloop added async loading method - Refactored frontend setting loader for reusability of settings file path - Added integrity check test for routes.yaml file		2020-09-10 10:54:57 +12:00
..
client@8f4a8cdf2d	Updated Ghost-Admin to v3.32.1	2020-09-07 12:06:05 +01:00
frontend	Added routes.yaml content checksum storage to the db	2020-09-10 10:54:57 +12:00
server	Added routes.yaml content checksum storage to the db	2020-09-10 10:54:57 +12:00
shared	Added minor member newsletter customisations via config	2020-08-24 10:44:22 +01:00
index.js	Refactored server announce functions to be clearer	2020-08-09 17:25:15 +01:00