* Start the xOne/xMany work
* Update update/upsert
* Finish updating itemsservice
* Add comments, add nested revisions on update
* Use new internal api
* Update collectionService to one/many structure
* Move files to one/many structure
* Move permissions to one/many structure
* Move relations service to one/many structure
* Move roles to one/many structure
* Move users service over
* Move webhooks to updated structure
* Move deprecated methods to the bottom
* Replace deprecated uses
* Use new methods in controllers, add batch update/delete by query
* Use updated methods in API
* Fix email being required
* Remove unnecessary DB call
* Fix batch update/delete validation
- Ports are not required here, as all three containers share the same 'directus' network. They can communicate with each other internally. Opening the ports only exposes the database and cache to the world (the internet) unnecessarily, posing more of a security issue.
- 'Container name:' ensures that the container adopts that specific name. While by default the container will start with the name specified at the top of each container section (i.e. directus, cache, database), if one of those names is occupied it risks reverting to an alternative, which will have networking implications as those specific hostnames are sought from the other containers. With 'container name:' set, it will return an error that the container name is in use. Adopting here the 'explicit is better than implicit' approach.
'Depends on:' as the name suggests, ensures that the database and cache are up and running before Directus starts.
