Resolved schedule operations after git pull event

[paskuale]

Server operating system version

Debian 10.13

Plesk version and microupdate number

Obsidian v.18.0.53

Hi, every time I pull from the repository I have a small difference in the .htaccess file that forces me to manually update each pull operation, is there a way to schedule the operation ?
Thanks

 

[EvgeniyKovrizhnikov]

Hello,

If you are using Git extension to pull your changes from a remote repo, you can use Deploy Action in Domain -> Git -> Settings (lower right corner of Git overview card). There you can enable "Enable additional deployment actions" checkbox and write any shell code you want. This code will be executed on every Deploy, both for manually from extension UI, and automatic using extension hooks.

 

[paskuale]

Thanks so much for the suggestion @EvgeniyKovrizhnikov , it was just what I was looking for he advises me to insert a command for each new line, but a command of this type works if I execute it from the shell, if I insert it as an addition deployment actions it does not recognize it. Where am I wrong?
the command is this:
/opt/plesk/php/8.1/bin/php ./bin/console cache:clear
error return this:
-: /opt/plesk/php/8.1/bin/php: No such file or directory
thanks

 

[EvgeniyKovrizhnikov]

Looks like the problem is in disabled SSH access in hosting settings. You can use this KB article - How to grant a subscription user SSH/SFTP access to its home directory in Plesk - Support Cases from Plesk Knowledge Base. I think that every option except "forbidden: or "chrooted" will works fine, but I tested it with /bin/bash and /bin/sh, and it works good for me.

 

[paskuale]

Great @EvgeniyKovrizhnikov it works like a charme

 

[paskuale]

Hi all,
I continue on this thread because the problem is close to the previous case... every time I run a git pull it overwrites (rightly) the .htaccess file, and I promptly have to update a string within the same file:

Options +FollowSymlinks

in -->

Options +SymLinksIfOwnerMatch

any suggestions to overcome this boring step ? Thanks

 

[Peter Debik]

Disabling "Restrict the ability to follow symbolic links" on the "Websites & Domains" > "Hosting & DNS" > "Apache & Nginx" page would allow you to use the "+FollowSymlinks" option. If you are no on a shared hosting environment and control your code yourself, it is a low risk change.