Applicable to:
- Plesk Onyx for Linux
Symptoms
Additional deploy actions for Git Repositories are not executed without full path in case they use commands located in /usr/local/bin/:
Cause
This is a Plesk bug with ID EXTGIT-22 , which is planned to be fixed in the future Plesk updates.
Resolution
As a workaround use one of these three possible solutions:
I.
- Log in to Plesk
-
Specify the full path to the command in Domains > example.com > Git Repositories > Repository Settings > Actions :
II.
-
Connect to the server via SSH.
-
Create a symbolic link in
/bin/directory to use the command without full path in Domains > example.com > Git Repositories > Repository Settings > Actions. For example:# ln -s /usr/local/bin/command /bin/command
III.
Allow access to the server over SSH for a user to /bin/bash as described here: How to give limited SSH access to Plesk domain's system user
Comments
19 comments
If I just want to run 'yarn' after each push what exactly should I write in the field?
@John Karamatsoukas
Use "/usr/bin/yarn" with the needed options
Alisa Kasyanova I did that and it still won't work, I can run the command from the terminal and it works. but it doesn't run from the git extension, additionally I wrote it into a bash script but same, nothing happens.
Maxim Krasikov When will this be fixed, it's very important now to have a smooth CI/CD workflow and the additional SSH commands are critical to make that usable, specially when we need process special processes after the automatic sync, thank you.
Motaz Elshazly we don't have any ETA for new for the fix.
Try changing Domains > example.com > Web Hosting Access > Access to the server over SSH to /bin/bash
Had the same issue, with the commands not working. Changing the "Access to the server over SSH" to "/bin/bash" fixed the problem. You don't even have to say /usr/bin/yarn. You can directly call yarn from additional command. Thank you so much!
Walter Jansen,
Thank you for sharing your user experience.
Anton Maslov's answer should be added as an alternative to the resolutions as an alternative fix.
Hello @DanielVagg
Thank you. Added.
neither cp, nor rm works - any workaround?
http://prntscr.com/qyydkx
Hi Mark,
You need to use the full path to cp and rm binaries. Please check your Linux distribution in order to know where they are located.
Also, specify the whole path for your domain (for example /var/www/vhosts/example.com/httpdocs/folder).
I am trying to deploy Docusaurus on a Plesk server. After pulling the latest code, I would like to run these commands to build html files:
As hitting the commands above from SSH returned an error because of a non existence of `node` command globally, I created symbolic links:
And even after modifying the original commands to include full paths, they don't seem to be working.
I tried allowing SSH access to `/bin/bash` but this did not help either.
Hello Hiromichi Suzuki
To deploy Node.js app with the help of Plesk, follow this guide: https://www.plesk.com/blog/product-technology/node-js-plesk-onyx/
Hi Hiromichi Suzuki, I use this in the additional deployment action:
(PATH=/opt/plesk/node/12/bin/:$PATH; npm i; npm run build)
Works like a charm. Also needs SSH access set to `/bin/bash`
Thank you Ivan and Clemens. I tried the command below too but this somehow does not work either. SSH access is set to `/bin/bash`. Without access to logs it is very difficult to further investigate the issue..
After hours of trying, I finally got it work.
In short, the commands must come in one line, like so:
I found that `touch test.txt` places the file under `/var/www/vhosts/example.com/docs.example.com` when the command is in the next line after `cd`. It appears that every line starts from the root directory, which kind of makes sense. So never really trust "Type each command on a new line." under the textbox.
npm is working, but i can't copy files from build to another folder.
Are there any logs? Maybe it's a permission problem.
rm -r /var/www/vhosts/xyz/build/;
/opt/plesk/node/12/bin/npm ci --scripts-prepend-node-path;
/opt/plesk/node/12/bin/npm run build --scripts-prepend-node-path;
rm -r /var/www/vhosts/xyz2/*;
/bin/cp -R /var/www/vhosts/xyz/build/* /var/www/vhosts/xyz2/;
Hello Hiromichi Suzuki
Thank you for the feedback. Glad to hear it finally worked.
@Mario Peters
You may enable Plesk debug as per https://support.plesk.com/hc/en-us/articles/213408889-How-to-enable-disable-Plesk-debug-mode (do not enable sql_query) and check /var/log/plesk/panel.log to see why exactly actions fail.
I have tested the mentioned behaviour and noticed two things:
1) At the beginning of the additional action, cd to deploy path is executed (e.g. cd '/var/www/vhosts/example.com/httpdocs'). So if you want to copy all files from /var/www/vhosts/example.com/httpdocs/build/, simply write "/bin/cp -R build/*" without the full path.
2) The command is executed on behalf of the example.com sysuser, so make sure it has permissions to write to the destination path.
Hiromichi Suzuki thank you so much. You just helped me so much by giving your brilliant one line of command. I was lost again but your answer was my remedy.
Please sign in to leave a comment.