Discover RoboFile.php on directories above the current one

[rodrigoaguilera]

It would be nice to be able to install robo globally and then be able to launch robo command from any folder in your project and get the same lists of tasks

[greg-1-anderson]

I don't know that it should search all the way up, but perhaps it could look in the repository root (via git rev-parse --show-toplevel), and maybe optionally REPO_ROOT/scripts/RoboFile.php.

@DavertMik what do you think?

[ahoendgen]

Also it would be nice if it´s possible to create a global RoboFile.php which provides default functions for all directories regardless they have a RoboFile or not

[greg-1-anderson]

@ahoendgen See http://robo.li/framework/

[greg-1-anderson]

Also https://github.com/consolidation/Robo/blob/master/examples/robo.script

[ahoendgen]

@greg-1-anderson thx

[amenk]

You can see n98/magerun for an implementation in PHP.

[greg-1-anderson]

@amenk n98/magerun appears to not use Robo. Which part of it were you recommending as a useful example?

Looking at your comment in #532 (comment), perhaps magerun execs Robo? You might want to consider adopting http://robo.li/framework/ as your base runner. If you do this, you could implemente magerun commands via the annotation mechanism Robo uses -- but you wouldn't have to rewrite any of your Symfony Console commands if you didn't want to. It's perfectly reasonable to mix the two styles, as the annotation mechanism simply produces Symfony Console commands. Just a thought.

In any event, a direct link to the parts of magerun that you think would be helpful here would be appreciated.

[amenk]

I know magerun does not use robo. But it has a detection logic for the Magento root which might be useful for detecting the Robofile Root as well ... It just goes back in the file tree until Magento was found. In our case, Robo could go back up in the tree until a Robofile was found. Git does something similar.