Ghost/core/server/api
Hannah Wolfe ed16998461 Restructure Configuration API endpoint
refs #6421, #6525

- The configuration API endpoint was a bit of an animal:
   - It's used currently in two ways, once for general config, another for the about page.
   - These two things are different, and would require different permissions in future.
   - There was also both a browse and a read version, even though only browse was used.
   - The response from the browse was being artificially turned into many objects, when its really just one with multiple keys
- The new version treats each type of config as a different single object with several keys
- The new version therefore only has a 'read' request
- A basic read request with no key will return basic config that any client would need
- A read request with the about key returns the about config
- A read request with a different key could therefore return some other config
2016-02-19 18:49:23 +00:00
..
authentication.js Harvest server side strings 2015-12-19 12:12:16 +01:00
clients.js Harvest server side strings 2015-12-19 12:12:16 +01:00
configuration.js Restructure Configuration API endpoint 2016-02-19 18:49:23 +00:00
db.js Backup database before deletion 2016-02-14 09:04:53 +00:00
index.js Add dynamic client_id/client_secret 2015-09-02 16:39:34 +01:00
mail.js Refactor mail service 2016-02-10 16:31:42 -06:00
notifications.js Harvest server side strings 2015-12-19 12:12:16 +01:00
posts.js Harvest server side strings 2015-12-19 12:12:16 +01:00
roles.js Refactor handlePermissions 2015-08-11 16:03:57 +02:00
settings.js Harvest server side strings 2015-12-19 12:12:16 +01:00
slugs.js Harvest server side strings 2015-12-19 12:12:16 +01:00
tags.js Harvest server side strings 2015-12-19 12:12:16 +01:00
themes.js Harvest server side strings 2015-12-19 12:12:16 +01:00
upload.js Harvest server side strings 2015-12-19 12:12:16 +01:00
users.js Harvest server side strings 2015-12-19 12:12:16 +01:00
utils.js Harvest server side strings 2015-12-19 12:12:16 +01:00