Difference between revisions of "Developers/Architecture"
From PartKeepr Wiki
(Created page with "= Introduction = PartKeepr uses [http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/reference/working-with-objects.html Doctrine Entities] for database handling...") |
|||
| Line 7: | Line 7: | ||
The ExtJS frontend communicates with the PHP backend using a [http://json-ld.org/ JSON-LD]-enabled [https://en.wikipedia.org/wiki/Representational_state_transfer REST API]. The | The ExtJS frontend communicates with the PHP backend using a [http://json-ld.org/ JSON-LD]-enabled [https://en.wikipedia.org/wiki/Representational_state_transfer REST API]. The | ||
| − | Thanks to the [https://github.com/dunglas/DunglasApiBundle Dunglas Api Bundle], a developer needs to write little to no code to make the REST API work. | + | Thanks to the [https://github.com/dunglas/DunglasApiBundle Dunglas Api Bundle], a developer needs to write little to no code to make the REST API work. See [[Developers/Entities#Creating_new_entities_and_registering_it_with_the_REST_API|the Entities]] documentation for further details. |
Latest revision as of 17:00, 4 November 2015
Introduction
PartKeepr uses Doctrine Entities for database handling and ExtJS for the frontend.
API First
The ExtJS frontend communicates with the PHP backend using a JSON-LD-enabled REST API. The
Thanks to the Dunglas Api Bundle, a developer needs to write little to no code to make the REST API work. See the Entities documentation for further details.
