Quick update on image hosting

By chance I looked at the storage space used on Scribbles for all the images that are uploaded, and then also each variant that is created afterwards — because it'll keep the original and then use that to make more optimised versions of those for rendering purpose on a post page.

What I noticed is that in the last few days alone, the storage used has doubled — which means it's been getting busy 🥳

The way I set it up initially is to have an attached drive to the server, which acts as the primary storage, and then it will automatically mirror these images offsite — in my case I chose AWS S3 because it's just so more reliable than I found with Backblaze B2 (sorry, technical, I know).

But... as it turns out, I nearly ran out of disk space on my attached drive (10GB). It was at 94% yesterday, which meant today I would have problems. The other thing now is that in order to increase the storage, which I did by mistake, is that I would have to bring that offline and manually resize it with some magic server commands. I didn't want that on an ongoing basis.

So I changed the way images are hosted now, with no changes to the way it works for you.

All images will now reside primarily on AWS S3 — where they were already because I have been mirroring since day 1. In addition to this, I added B2 as the mirror location. This is nothing hard to do — it's all built into the framework. Because B2 is so slow it was best to have it there as a backup and puts my mind at ease.

Saying all that, everything should be working just fine and as it should — you should see and feel absolutely no difference — however if something is amiss, just let me know.

At least now I know that I don't have to worry about disk space — just the bill 😅