Closed ywarnier closed 11 years ago
Probably the phar is not updated. I just found that I did not commit the vendors.
I test it in zap and it doesn't work. I did a little research and it seems that the trouble maker whas suhosin.
I did a clone in zap and it works fine with:
php -d suhosin.executor.include.whitelist="phar" chash.phar
I also thought the problem was the vendor directory, but on my computer it worked fine, and I had just cloned it from here, so not the problem (I suppose it was automagically downloaded by createPhar?). Interesting to find that suhosin was the problem. How did you find that out?
Anyway, the issue itself has been solved. Thanks! Good job on editing the readme.
Hi, On our server "zap", chash doesn't say anything when launched. I first thought it would be some kind of php config problem, but there no error reporting (even when forcing it through display_errors and log_errors) and no permission problem (directory in 0777). When launching from the chash directory directly and using the CLI command:
php chash.phar
I get no output. When launching php5 chash.php, it reports not being able to load Composer's autoload:
PHP Warning: require_once(/tmp/chash/vendor/composer/autoload_real.php): failed to open stream: No such file or directory in /tmp/chash/vendor/autoload.php on line 5
Is there anything special I need to do first? Maybe install composer? Why would it be working on my computer but not on the server? I don't know Composer much, nor Phar, so the lack of logs gets me confused.