A screenshot of a cloud disk configuration page for Backblaze B2 cloud storage. The configuration form includes fields such as Disk (set to S3), Key, Secret, Region (us-east-005), Bucket (beware-pixelfed), Endpoint (s3.us-east-005.backblazeb2.com), Visibility (public), and URL (https://beware-pixelfed.s3.us-east-005.backblazeb2.com). Sensitive information in the Key and Secret fields is blacked out for security reasons.

Notices where this attachment appears

1. Embed this notice
   BeAware :fediverse: (beaware@social.beaware.live)'s status on Monday, 15-Jul-2024 05:57:19 JST BeAware :fediverse:

   So, I've been trying to get this Pixelfed instance hooked up with Backblaze object storage.

   I host it with Elest.io because it's managed and I'm not too versed in linux, though I get by.

   When I started the instance and messed around in the Admin UI, I noticed these "cloud storage" settings, which I filled out as such. (First pic) but it kept giving me an error about the credentials being incorrect (they're not, i copied them directly from backblaze)

   Then, while trying to get help for that, someone told me to edit the ENV with these options:

   ## S3 Configuration
   PF_ENABLE_CLOUD=true
   FILESYSTEM_CLOUD=s3
   AWS_ACCESS_KEY_ID=
   AWS_SECRET_ACCESS_KEY=
   AWS_DEFAULT_REGION=
   AWS_BUCKET=
   AWS_URL=
   AWS_ENDPOINT=

   But, when I go to my ENV file. Some of those options aren't even there. (second pic).

   Can I just insert them at the bottom and put the info in there, and it would work?

   Also, for AWS_URL and AWS_ENDPOINT, do I need to include https://?

   Any help would be appreciated. Thanks.

   #Pixelfed #Fedi #Fediverse #ActivityPub #FediAdmin