Damien
My feedback
6 results found
-
5 votes
An error occurred while saving the comment -
45 votes
Thank you for your input. We will consider this functionality in upcoming releases if it is popular. Everyone, please continue voting for this feature if you consider it important.
—
IG -
103 votes
Hi everyone,
This seems to be important, so we’ll address it in one of the upcoming Plesk releases.
Please continue to vote so we can accurately assess the popularity of this request.
— AK
-
238 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
— AY
-
55 votes
Thank you for your input! We will consider this functionality in upcoming releases if it will be popular.
Everyone, please continue voting for this feature if you consider it important.
—
IG -
70 votes
An error occurred while saving the comment These are remote services, so they can only scan webpage output. They are defacement monitors.
The feature here is filesystem based, so it would identify new unknown files, or backend changes to files that may not cause any change to generated HTML)
Logging is essential - especially because:
* git actions are executed using a different shell (/bin/sh) vs. whatever is configured for the system user (so environment or other nuances may cause unexpected errors)
* errors are silent and fatal (the commands appear to executed as "command1 && command2", so command2 will only be executed if command1 has a clean exit code)
* execution starts from the git deploy directory (not the system user home directory), so again this can be a source of user error when specifying the commands
* troubleshooting and debugging all of the above is awkward: you have to write your own log files (e.g. redirecting command output) which is not at all elegant or intuitive for a typical developer who just wants to get their stuff deployed and working!