Oh, that should be quite simple then. Though if it’s not too big, maybe it’s just less hassle to use AWS S3? Their pricing isn’t too bad for storage, it’s just kind of hectic for bandwidth.
I think you’d just need to put this in your app.yml with the correct info and rebuild. It’s excluding the parts that are for user uploads. You wouldn’t need to include the after_assets_precompile other part from the tutorial.
Just SSH into your server as root then run:
cd /var/discourse
nano containers/app.yml
Use the keyboard arrows to move the curser around and paste in the info below underneath the part of the file that says: #DISCOURSE_CDN_URL: https://discourse-cdn.example.com
DISCOURSE_S3_REGION: "us-west-002"
DISCOURSE_S3_INSTALL_CORS_RULE: false
DISCOURSE_S3_ENDPOINT: https://s3.us-west-002.backblazeb2.com
DISCOURSE_S3_ACCESS_KEY_ID: myaccesskey
DISCOURSE_S3_SECRET_ACCESS_KEY: mysecretkey
DISCOURSE_S3_BACKUP_BUCKET: falcoland-files/backup
DISCOURSE_BACKUP_LOCATION: s3
Make sure you’ve put the correct info in for the region, endpoint, access key, secret key and backup bucket name.
Press ctrl+o and confirm to save, then press ctrl+x to exit. Then run:
./launcher rebuild app
Fairly confident it should work fine.
Seeing you are on Digital Ocean, it’d be a good idea to make a backup before you do this though. So rolling back is easy if something goes wrong.