-
-
Notifications
You must be signed in to change notification settings - Fork 266
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
BACKBLAZE_HOST_URL ? #393
Comments
ok got it BACKBLAZE_BUCKET is bucket name instead of bucket id |
You were able to get it working? Sorry there's not a ton of docs rn |
@kgnfth yes but it still tries to locate the file from the local folder |
if i set if i set but i dont want it to save it to the local folder i thought it would serve the files from the bucket |
@kgnfth do you have |
@kgnfth |
@kgnfth thos where stripped out soo not too worry So i have to change like this im not an expert but i think based on this code uploadServer =
|
this is what i get
using thing env
Correct url to the file is https://f003.backblazeb2.com/file/nodetubetest/deejavu/4TScUOF.jpeg |
Is it the link to the file on the actual upload server though? |
I assume the file was uploaded from your nodetube instance, right? So backend is not a problem. |
@BassOfBass it uploads correctly but the serve url is wrong |
Okey finally i made it work the correct settings are like this
but the importer still uses local folder |
Okay thanks for this @kgnfth I'll consult this when writing up the docs for Backblaze. And yeah importer would need a bit of a touch up to add the uploading to backblaze function. I can show you what code to copy and where if you'd like to submit a PR for that. Thanks also for the help @BassOfBass |
@mayeaux If you could point me in the right direction I could take a crack at it. |
@l1ghtsword The files to shuffle through:
|
Hello
what do i have to put at BACKBLAZE_HOST_URL
https://bucketname.s3.us-west-001.backblazeb2.com/
or
s3.eu-central-003.backblazeb2.com
i keep getting this error
Uncaught Exception: Error: bucket 05662bb3f3... could not be found
The text was updated successfully, but these errors were encountered: