kane-mason

or just reread settings everytime `getSetting` is called, and remove `req.settings` in favor of `getSetting`

@thomas4019 id be happy to do PR for this if you could advise which direction you like? Something else to consider is having two instances of expressa where an update...

Mmmmm the more i think of this the more i dont like performing another read from the db on every request. Will carry on thinking, but for now i wrote...

A work around for this could be that settings collection is readonly - this could be a rule written into expressa using permissions, so a user may opt out of...

Sorry @thomas4019 i missed this! So i have made my settings read only by way of permissions and it is working nicely. I created a collection to store configuration that...

i think we should make these read only by default

no not running into performance problems yet, but just trying to think of the future and something like redis seems to be commonly done and i thought there may be...

ok yes the description does get preserved. two other properties that also get nuked are `media` and `links` 

@thomas4019 i had a bit of a play around with it and it seems to be good! One bug i found is that if the `required` array is not present...

@thomas4019 any progress on this?