Call a .phar executable from inside a web app controller

Question

I need to run composer.phar update from a web controller.

I can run all kinds of regular commands in this way (ls, cp, etc) but when I invoke the phar file I get empty output.

The code I have looks like this:

class Maintenance_Controller
{
    public function do_maintenance()
    {
        echo exec("/usr/bin/env php composer.phar", $out, $ret);
        var_dump($out); // outputs -> array()
        var_dump($ret); // outputs -> int(127)
    }
}

127 indicates a bad path, but I am sure I'm in the right directory.

Also, this works when using a php_cli wrapper, so maybe it has to do with the www-data user? chmod 777 does not help, and I hate to do that anyway.

I have also used passthru(), system() and the backtic syntax. I am unable to get to the reason this doesn't work. I can't seem to interrogate the stderr or stdout from the exec() call beyond the 127 code.

Obvious Question:

What am I doing wrong?

Better Question:

Is there a better way to interrogate and execute .phar files from within a script?

Is there a reason your using `passthru` instead of `exec`? – prodigitalson Dec 07 '12 at 01:46 — prodigitalson, Dec 07 '12 at 01:46

score 3 · Accepted Answer · edited May 23 '17 at 11:51

3

UPDATE:

From this question:

Value 127 is returned by /bin/sh when the given command is not found within your PATH system variable and it is not a built-in shell command.

Try using exec('php composer.phar', $out, $ret); and see if that works. You might also need to use the full path to php if its in a non-standard location which you can probably get from which php.

Im not sure why you are using passthru here. I would use exec for better handling. Id use exec here instead of passthru

class Maintenance_Controller
{

    public function do_maintenance()
    {
        exec("composer.phar update", $out, $ret);
        if(!$ret) {
            // handle success
        } else {
           // handle error
        }

    }
}

This way you have all the output by line in $out as well as the shell return val (0 if ok, > 0 if not). If you wanna get really fancy you can loop over $out and scan for the errors and then build and exception to throw.

edited May 23 '17 at 11:51

Community

1
1

answered Dec 07 '12 at 01:48

prodigitalson

60,050
10
100
114

yeah exec is a better idea. Updated question to use `exec()`. – willoller Dec 07 '12 at 01:53
Good suggestion - same issue using "/usr/bin/env php composer.phar update" – willoller Dec 07 '12 at 21:42
1

Did you try with the full path to `php` instead of executing through `env`? – prodigitalson Dec 08 '12 at 00:39
I think you can use `PHP_BINDIR` for the full path. Not sure which versions that covers though. – prodigitalson Dec 08 '12 at 20:40
Turns out the www-data user has a practically empty `$PATH`, so `PHP_BINDIR` is null. It's a linux problem now, not a php problem. – willoller Dec 09 '12 at 19:08
Add it to the global `.rc`? – prodigitalson Dec 10 '12 at 05:36

Call a .phar executable from inside a web app controller

Obvious Question:

Better Question:

1 Answers1