Other information we'll need from the previous process is the 'Friendly URL' from the list of URLs we got after uploading our test file to Backblaze. Remember what you set, as we'll be creating a CNAME for it in the next step. This could be, or - it doesn't matter what you choose, it just needs to be a different domain/sub-domain to your Mastodon instance. The only thing we'll do differently to the previous post is, when asked: 'Do you want to access the uploaded files from your own domain?' say yes, and enter the domain or subdomain you want to use. Again, while this is aimed at setting up S3 storage for Mastodon, the bucket setup, API key setup are equally relevant for any other application. You'll need to sign up for a Backblaze account and follow the bucket setup instructions over on my previous post: Using Backblaze B2 (S3) Storage with Mastodon. There are a few bits where I've done it differently or their steps didn't work, but if any of what I've written here doesn't work for you, take a look at their post for a second opinion. However, Backblaze are a founding member of Cloudflare's 'Bandwidth Alliance', which means any Backblaze B2 content you serve via Cloudflare, is completely free!īackblaze have a blog post about this process which I followed as closely as I could. The highest-looking charge here would appear to be the $0.01 per GB downloaded. For what we're looking at here, the bulk of these would be file uploads to your bucket using S3 calls)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |