Developers/Re-generating the environment

From PartKeepr Wiki
Revision as of 01:10, 10 June 2016 by Felicitus (talk | contribs)
Jump to: navigation, search

Re-generating the environment ensures that all caches and generated files are up to date.

This is especially important after changes you apply to your parameters.php since Symfony2 caches the parameters file in the production environment.

The easiest method is to re-run setup; simply click next on all questions.


  • 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.
The above commands must be ran as the user which your webserver runs as, or you have to chown the files to the correct user

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