Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Modules can be used for code-reuse at the project level:</p> <p><a href="http://framework.zend.com/manual/en/zend.controller.modular.html" rel="nofollow noreferrer">http://framework.zend.com/manual/en/zend.controller.modular.html</a></p> <p>If you have a new project that is similar in functionality to an existing one, you can add a new module to your existing project and turn specific modules on/off in the application.ini file. Module-specific initialization can be contained in their own Bootstraps.</p> <p>But it isn't completely straightforward...</p> <p>When I tried a few months ago, Zend_Tool had issues creating the module directory structure and I had to create it by hand. Also, some features you might require (module-specific configuration files, merged navigation definitions, and/or specific deployment configs) are not built into Zend Framework currently and would need to be written.</p> <p>For my setup I have an application.ini for each deployment (application-foo.ini, application-bar.ini). Using an environment variable (SetEnv APP_DEPLOYMENT foo) set in the .htaccess file, the appropriate ini file is chosen via custom logic in the bootstrap (index.php). Generic configuration for the modules are put into module-specific configuration files, loaded via a custom subclass of Zend_Application_Resource_Modules.</p> <p>A deployment process can be run to exclude any unneeded modules, public files and/or libraries depending on the site. Phing, Capistrano, or Ant is good for that.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload