Fabien O'Carroll 2e922808e8 ♻ Updated naming for Content API specific middleware ... no-issue This is because the Content API will eventually be accessed not just from Content API keys. The addition of a Content API specific authorization middleware is because: 1. content api should not authorize based on req.user 2. content api will need separate authorization than admin api		2018-11-08 13:34:29 +07:00
..
adapters
api	🚧 Added req.member to the v2 api context object	2018-11-08 13:32:41 +07:00
apps	Renamed /users to /authors for Content API V2 (#10096)	2018-11-07 15:29:37 +01:00
config	Parsed nconf env values (#10077)	2018-10-28 20:06:44 +01:00
data	Changed casper.ghost.org to static.ghost.org references (#10109)	2018-11-07 15:50:38 +01:00
helpers	Renamed /users to /authors for Content API V2 (#10096)	2018-11-07 15:29:37 +01:00
lib	Added Node v10 Support (#10058)	2018-10-30 15:45:51 +07:00
models	Renamed /users to /authors for Content API V2 (#10096)	2018-11-07 15:29:37 +01:00
public
services	♻ Updated naming for Content API specific middleware	2018-11-08 13:34:29 +07:00
translations	Renamed /users to /authors for Content API V2 (#10096)	2018-11-07 15:29:37 +01:00
views
web	♻ Updated naming for Content API specific middleware	2018-11-08 13:34:29 +07:00
analytics-events.js
filters.js
ghost-server.js
index.js
overrides.js
update-check.js	Migrated update check to use api v2	2018-10-18 00:13:31 +02:00