-
Notifications
You must be signed in to change notification settings - Fork 171
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 requst: s3 backend path prefix #316
Comments
camathieu
pushed a commit
to camathieu/plik
that referenced
this issue
Sep 28, 2020
camathieu
pushed a commit
to camathieu/plik
that referenced
this issue
Sep 28, 2020
camathieu
pushed a commit
to camathieu/plik
that referenced
this issue
Sep 28, 2020
camathieu
pushed a commit
to camathieu/plik
that referenced
this issue
Sep 28, 2020
camathieu
pushed a commit
to camathieu/plik
that referenced
this issue
Sep 28, 2020
camathieu
pushed a commit
to camathieu/plik
that referenced
this issue
Sep 28, 2020
camathieu
pushed a commit
to camathieu/plik
that referenced
this issue
Sep 28, 2020
camathieu
pushed a commit
to camathieu/plik
that referenced
this issue
Sep 28, 2020
camathieu
pushed a commit
to camathieu/plik
that referenced
this issue
Sep 29, 2020
camathieu
pushed a commit
to camathieu/plik
that referenced
this issue
Sep 29, 2020
Implemented in 1.3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
First off, great work adding the s3 support! This is a very coveted feature. I would only suggest adding a small improvement - path prefix support. Correct me if I'm wrong, but as of the latest release, plik writes to the root of the bucket.
In our use case we:
Having a config option to set a path prefix for the storage in the bucket would really be the selling point.
Thank you!
The text was updated successfully, but these errors were encountered: