Skip to content
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

Enhancement: Metadata for files uploaded via native protocol #78

Open
HAL9000COM opened this issue Dec 15, 2023 · 1 comment
Open

Enhancement: Metadata for files uploaded via native protocol #78

HAL9000COM opened this issue Dec 15, 2023 · 1 comment

Comments

@HAL9000COM
Copy link

What did you do?

Upload files via Storj native protocol and access them via the gateway.

What did you expect to see?

Files should have metadata.

What did you see instead?

Files have no metadata.

Files uploaded via uplink cli or filezilla won't have metadata when accessed via the gateway, which have compatibility issue with S3 client (e.g. Nextcloud will always report "no ETag" error).
I understand that Stroj native protocol does not upload metadata, but can this be solved by enhancement of the s3 gateway?
Can such metadata be generated once accessed via the gateway, or some command that scan the bucket and create missing metadata?
Related issue: #storj/storj#5424

@amwolff
Copy link
Member

amwolff commented Feb 14, 2024

I understand that Stroj native protocol does not upload metadata, but can this be solved by enhancement of the s3 gateway?

Objects uploaded through the gateway will have the necessary metadata. If you need S3-related metadata, it's best to use the gateway to upload them. Gateway-ST (this repository) has similar self-hosting capabilities to Uplink CLI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants