I had got a warning in my command line about disc space before rebuilding my container while installing a Discourse plugin. I had to run some commands to remove some older versions of linux on my digitalocean droplet, but I’m still over 50% ssd capacity.
As my Discourse website has grown, I started looking at storage solutions. I’m currently on a 5$ digitalocean droplet and have read around about digitalocean block storage and amazon s3. I see the S3 settings built into the Discourse settings, so I’m guessing its easier to setup.
What do you use for your website? Which has better loading speeds, s3 vs digiocean blocks? What option is cheaper? Wouldn’t the free tier of s3 make it cheaper than digiocean blocks? Do you store your images AND backups? Or do you recommend another option outside of digiocean and amazon?
Would the free tier of Cloudflare work as the CDN in front of the bucket? I already use them with my domain settings for the free DDOS protection.
I noticed DigitalOcean advertises their Spaces service is cheaper than the other well known providers. So that’s definitely a plus.
Because the CDN that comes with DigitalOcean Spaces doesn’t work correctly with Discourse, I’m thinking I should just go with one of the other providers on your list. That way I don’t have to pay for DigitalOcean Spaces and a separate CDN service.
A missing content-encoding in the DO CDN implementation definitely is a bummer, but it only happens when setting all the S3 parameters inside app.yml. If those parameters are set in the site settings via web admin console, the DO only serves the S3 uploads via CDN, and the site assets are still served from the source.
It seems that this is by design, because the DISCOURSE_S3_CDN_URL env variable, if set in the app.yml, overrides the CDN setting for assets too, while this same setting, when declared in site settings only, doesn’t?
This is a bit inconsistent, but it allows the DO CDN to be used for S3 uploads only, without breaking the site:
There are two ways to do this:
declare all S3 settings in site settings only
shadow all S3 settings exceptDISCOURSE_S3_CDN_URL in the app.yml, and declare DO CDN in SiteSetting.s3_cdn_url