Q: NC21 in Docker - Flow Script not Activated about workflow_script

[LinuksGuru]

I copied this script (inside NC Docker) into 2 addtional dirs
/bin
/var/www/html (where NC lives)

No changes, doesn't work, flow.log is empty.

[LinuksGuru]

I changed rule, File rename -> name matches -> /ok/i
Script still not invoked after file have been renamed (e.g. report.ods to report ok.ods). NextCloud sees script, since if it doesn't exists, it throws error when trying to save settings.
And NO log entries in nextcloud.log and flow.log which could indicate any info about this script. NextCloud/apache in docker, updated just today. Custom flow app also last version.

[blizzz]

Are background jobs running there?

[LinuksGuru]

Yes, background jobs are running. BTW, I'm was able to (partially) solve this problem. Script IS activated only if it's located inside NC data directory. Any location outside NC data dir, e.g. /opt, /usr/bin, whatever, and no success, and no error message anywhere.

Additionally, NC 21 Docker/Apache (from Docker hub) comes with a security mechanism that prevents custom flow script to run anything from /usr/bin, for example, making it utterly useless. I added www-data to "users" group, no changes. Using sudo would be too awkward and complex because of too many options required in /etc/sudoers.

How to fix this? Thanks in advance.

[blizzz]

Additionally, NC 21 Docker/Apache (from Docker hub) comes with a security mechanism that prevents custom flow script to run anything from /usr/bin, for example, making it utterly useless. I added www-data to "users" group, no changes. Using sudo would be too awkward and complex because of too many options required in /etc/sudoers.

How to fix this? Thanks in advance.

As this seems to be a setup issue I would like to ask you to raise your question in the forums: https://help.nextcloud.com