-
Notifications
You must be signed in to change notification settings - Fork 167
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
[Feature Request] add read-only share-url #430
Comments
Hello @tionis, I think this feature already exists. For example upload a file on plik.root.gg (while not being authenticated). You will be able to add/remove file to the upload but as soon as you refresh the page you'll lose the UploadToken and you will not be able to perform those actions anymore. If you want to keep the read-write permissions you can use the "Admin URL" button to add the UploadToken to the URL, then refresh the page with this URL and you'll still have the read-write permissions. |
I see, do you know which version plik.root.gg runs on? |
It runs a dev build only a few commits behind master at : be8915d (1.3.5+) |
What version of the docker image are you running ? The UploadToken feature is really not recent. |
Ok, weird I will have to investigate this later, my instance is at https://yeet.digital, I guess we can consider this closed then? |
I did a test on your instance and it seems to work :) Read Only : Read Write : |
Ah yes, it works great, thanks! |
You are very welcome.
…On Tue, 10 May 2022, 10:25 Tionis, ***@***.***> wrote:
Ah yes, it works great, thanks!
—
Reply to this email directly, view it on GitHub
<#430 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABQ5XPWOXLPNIHEX7GTJNNLVJIMQLANCNFSM5TD6ARSQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Add a read-only share-url so that each time you generate a share you get a read-only url which only allows listing files and downloading them and a read-write-url which allows changing the share like normal.
The text was updated successfully, but these errors were encountered: