[fw-general] Easy ZF projects deployment with capistrano

2011-05-03 Thread Fabio Napoleoni
I really some RubyOnRails tools, I think they are very DRY, and I'm very impressed by Capistrano, a RoR deployment tool. So I tried to do something similar because I have a lot of Zend Framework projects and every time I need to deploy a new version of any of that is a little pain. I just

Re: [fw-general] Easy ZF projects deployment with capistrano

2011-05-03 Thread Juan Felipe Alvarez Saldarriaga
Hey! Grate work Fabio, and thanks for sharing this with us, I was using just capistrano without the rails feature, but this is better, I'll try it at night :). Thanks. On 5/2/11 8:31 PM, Fabio Napoleoni wrote: I really some RubyOnRails tools, I think they are very DRY, and I'm very

[fw-general] Module Bootstrap

2011-05-03 Thread Simon Walter
Is there a way to completely disable a module? Would generating 404 from the module's bootstrap be sufficient? How about the autoloader? Is there a way to stop that? I'm making a module registry system with dependency. So a module should not be accessible at all, unless certain requirements

Re: [fw-general] Module Bootstrap

2011-05-03 Thread Mark Harris
Hi Simon, Is there a way to completely disable a module? Would generating 404 from the module's bootstrap be sufficient? How about the autoloader? Is there a way to stop that? You can remove the module from your resources.modules listing so the controllers for that module are not

Re: [fw-general] Module Bootstrap

2011-05-03 Thread Simon Walter
On 04/05/2011 09:21, Mark Harris wrote: Hi Simon, Is there a way to completely disable a module? Would generating 404 from the module's bootstrap be sufficient? How about the autoloader? Is there a way to stop that? You can remove the module from your resources.modules listing so the

Re: [fw-general] Module Bootstrap

2011-05-03 Thread Mark Harris
Hi Simon, I need to be able to do some tests and then if the requirements are not met, disable the module so that it cannot be used. I think, then a good solution would be: Zend_Controller_Front::getInstance()-removeControllerDirectory($module); That would effectively remove all

Re: [fw-general] Module Bootstrap

2011-05-03 Thread Simon Walter
On 04/05/2011 10:53, Mark Harris wrote: Hi Simon, I need to be able to do some tests and then if the requirements are not met, disable the module so that it cannot be used. I think, then a good solution would be: Zend_Controller_Front::getInstance()-removeControllerDirectory($module);

Re: [fw-general] Module Bootstrap

2011-05-03 Thread Oscar Merida
On Tue, May 3, 2011 at 10:20 PM, Simon Walter si...@gikaku.com wrote: From looking at some of the module related methods of Zend_Controller_Front, I'm wondering if the dispatcher(?) scans *all* the module directories and does some bootstraping or loading of all modules regardless of if they