Wrong path to captainhook-run with run-mode: docker (v 4.5.7= about captainhook

[sebastianfeldmann]

With version 4.5.8 you can use the command option to define the custom path.

captainhook install --run-path=./vendor/bin

Or set it in the settings section of your configuration file.

{
 "settings": {
  "run-path": "./vendor/bin"
 }
}

Hope that helps :)

[shochdoerfer]

Can confirm: Works - Thanks for the quick help!

[shochdoerfer]

Setting "vendor-directory" in the configuration also had no effect on that. Not sure what this is supposed to be for though.

[sebastianfeldmann]

Currently CaptainHook assumes, that your current working directory is you git root.
Since the git root is located in /var/www is uses ./html/vendor... to access the binary.

I will add a config setting to overwrite the path guessing behavior

[shochdoerfer]

@sebastianfeldmann thx. Can't I fix this with setting "vendor-directory" then? I tried an absolute path and a relative path but that did not change anything in the bash script.

[shochdoerfer]

Easy fix for now: Move the .git folder into a separate location so that the relative path lookup will fail. This will lead to having the absolute path in the bash script and things are working again.

[sebastianfeldmann]

If that's possible for you that's a solution :)
As long as the vendor directory subsides inside the git directory the Cap'n will use a relative path.

New config option will be available in 5 - 10 minutes ;)

[sebastianfeldmann]

I will close this for now, if the issue isn't fixed with the run-path option feel free to reopen this issue ;)