bd597db829
- This is part of the quest to separate the frontend and server & get rid of all the places where there are cross-requires - At the moment the settings cache is one big shared cache used by the frontend and server liberally - This change doesn't really solve the fundamental problems, as we still depend on events, and requires from inside frontend - However it allows us to control the misuse slightly better by getting rid of restricted requires and turning on that eslint ruleset
10 lines
468 B
JavaScript
10 lines
468 B
JavaScript
/**
|
|
* Why hasn't this been moved to @tryghost/settings-cache yet?
|
|
*
|
|
* - It currently still couples the frontend and server together in a weird way via the event system
|
|
* - See the notes in core/server/lib/common/events
|
|
* - There's also a plan to introduce a proper caching layer, and rewrite this on top of that
|
|
* - Finally, I'm not sure if this shouldn't be two things - a cache, and a cache manager (the update system)
|
|
*/
|
|
module.exports = require('./cache');
|