Hello @2010!
I see there is interest about multi-fab implementation. I agree that my
solution with traversing is auto-magical and may lead to strange
behaviours and hard debugging.
Here is what I think multi-fab behaviour needs:
- easy (no boiler-plate code) integration between fabfiles
- less
On Sat, Jan 2, 2010 at 8:01 AM, Domen Kožar do...@dev.si wrote:
Hello @2010!
\o/
Here is what I think multi-fab behaviour needs:
- easy (no boiler-plate code) integration between fabfiles
- less or no magic
- covers most use cases + scaling
- be Python
- override-able with parameter
Hi all,
I've updated http://code.fabfile.org/issues/show/122 since it seemed
relevant to this discussion.
The most obvious solution seems to be to make ~/.fabricrc a full
fabfile of sorts and to simply process it prior to loading the main
(per-project / based on user's cwd) fabfile. (Or leave it
