Difference between revisions of "Developers/Getting Started"
From PartKeepr Wiki
(Created page with "{{note|This documentation doesn't apply to PartKeepr 0.1.9 or earlier}} {{note|This documentation doesn't apply to [https://github.com/partkeepr/PartKeepr/tree/master git mast...") |
(No difference)
|
Revision as of 11:29, 7 October 2015
This documentation doesn't apply to PartKeepr 0.1.9 or earlier
This documentation doesn't apply to git master commit 0ec91393ff81726c9c25683b6729519791ce5705 and earlier
Source Code Structure
PartKeepr's directory structure mostly follows the Symfony Best Practices.
Frontend
Currently, all frontend code resides in src/PartKeepr/FrontendBundle/Resources/public/js.
If you are using the dev environment, changes to the files should be immediately be visible.
For the prod environment, you need to call
app/console cache:clear --env=prodin order to rebuild the cache
Backend
We use one bundle per major functionality in PartKeepr. This is in contrast to the Symfony2 best practices where all logic resides in one AppBundle bundle.
The reason for that is that the code base is so large, that the structure would become quickly confusing.
