The discussion revolves around cleaning up the S3 assets folder. Benjamin_D noticed a buildup of assets in their bucket after experiencing a timeout during a rebuild, and is considering a cleanup. Wolftallemo pointed out that Scaleway S3 was having issues, but also suggested that deleting old asset files may not be worth the time, as it would only save a few cents in storage costs. Don shared their experience of deleting the assets folder and rebuilding, but now recommends renaming the folder, running a rebuild to verify everything works, and then deleting the old folder.
I’m using Scaleway object storage for nearly 2 years now, almost flawlessly, but for the first time S3_upload has timed out during the last rebuild, network issue? maybe… worked the second time, but it made me looked inside the bucket and I was surprised to see the assets piling up:
Although if there’s a lot of old asset files, deleting the old ones may save you a few cents in storage costs, but I wouldn’t consider that to be worth spending the time to remove the old ones.
I am using Object Storage for Uploads (S3 & Clones) and it used to be that I deleted the assets folder and run rebuild uploaded only the latest, current files again. But as you write you can rename the assets folder and run a rebuild to check everything works fine. After it creates and upload the new files you can delete the old assets folder.
, I don’t have any cdn configured, this is a tiny tiny tiiiiny instance)