-
Notifications
You must be signed in to change notification settings - Fork 479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permission denied running post-finish hook #921
Comments
I hope you mean chmod +x post-finish. Otherwise, you would remove the executable bit. However, looking at your last screenshot, the file seems to have the correct permissions set. Can you execute Also, I noticed in your first output that there is a space after the hashbang (#!). Try removing it because I do not know if this is allows there. |
Ok, I can reproduce the first issue:
Let's see what we can do. |
Maybe the problem is that
|
I am no Docker expert, so I don't really know where to go from here. Maybe @thirsch can help, who worked on the Docker image in the past. |
should probably stay on the first setup with the tusproject/tusd image and get that working |
It's great to hear that you found a solution! |
When i upload a file, i get a permission denied when the post-finish hook executes
i have a simple post-finish script just to check things are working
when i upload a file i get
permission denied.
if i try and run that file from the directory i get permission denied
i've ensured it is executable by running chmod -x post-finish etc
To Reproduce
Steps to reproduce the behavior:
have tus running as a container, activate hooks, put a post-finish file in the /srv/hooks folder
make it executable chmod +x post-finish
upload a file in the browser and then log out "hello" at the moment but will want the $TUS_ID and to change the file name
Expected behavior
the script to execute,
next stage is to rename the file from id to original filename with ext
How do you log info to the logs? of course echo isn't the cmd to use
and want to use the $TUS_ID var
The text was updated successfully, but these errors were encountered: