Difference between revisions of "Developers/Re-generating the environment"
From PartKeepr Wiki
(→Re-generate the environment) |
|||
Line 17: | Line 17: | ||
The default environment is '''prod''' if you skip '''-Denv'''. | The default environment is '''prod''' if you skip '''-Denv'''. | ||
+ | |||
+ | If you are running PartKeepr from an official archive release, you can simply use: | ||
+ | |||
+ | <pre> | ||
+ | phing regenerate-environment | ||
+ | </pre> |
Revision as of 20:55, 26 November 2015
PartKeepr uses quite a few helper bundles from Symfony2:
Introduction
- NFQ-Alpha Sprite Generator creates a CSS sprite sheet from individual icons
- If you add sprite sheets, you must run php app/console nfq:sprite:generate. This must be done prior assetic:dump.
- Doctrine Reflection Bundle generates ExtJS Models from Doctrine Entities
- If you change the Doctrine entities, you must run php app/console generate:extjs:entities to re-generate the ExtJS Models.
- Assetic combines and minifies the source JavaScript
- If you change JavaScript source, you must run php app/console assetic:dump to minify the JS files. Note that this should not be required if you are using the dev environment.
Re-generate the environment
In order to make re-generating the environment easier and consistent, you can use phing. PartKeepr provides a build.xml file. To re-generate the environment, call:
phing -Denv=yourenvironment regenerate-environment
The default environment is prod if you skip -Denv.
If you are running PartKeepr from an official archive release, you can simply use:
phing regenerate-environment