Your first pull zone was for uploads, this new pull zone will be for backups.īunnycdn dashboard>pull zones>add pull zoneįollow the same guide I linked to earlier, Bunn圜DN’s “How to Speed up your Backblaze B2 file delivery with Bunn圜DN” but this time you would link the new pull zone to your backup bucket instead of your uploads bucket. On your Bunn圜DN dashboard, you should create a second pull zone. It’s important to make automated backups of Discourse just in case anything breaks, then you can load your backup and fix it. The other bucket is private, this is your backup’s bucket. One bucket is public, this is your uploads bucket for your users to upload images on your forum. In the guide I posted higher in this thread, pay attention to how he explains you need two separate buckets.

If you want to setup your Discourse backups to go into your backblaze bucket, you need to do this: Now, every time someone uploads an image, it will be in your backblaze bucket and not taking up room on your digitalocean droplet The url should look different than your normal domain, it should be something like / filename Inspect the test image element, or view the images source to make sure it worked. Press ctrl+f5 twice in your browser on your discourse site.ĭo a test by uploading an image in the discourse text composer. Save the changes in Discourse admin setting area. The url should like something like this: but you will need to make sure you put in front of it like this: Go to your bunnycdn dashboard>pull zones>manage pull zones>click your zone> copy the url next to “host name”

After you create your Bunn圜DN pull zone, you need to get the correct url to insert into your Discourse admin backend setting for “s3 cdn url”.

Backblaze cdn