Backing up media cache
-
I think the thread title might have caused some confusion. I originally started this thread because I was having issues with backups. I managed to resolve those for the most part by aggressively clearing the cache, so I postponed the S3 topic.
However, my (public) instance has continued to grow since then, and some users are posting plenty of pictures and videos. As a result, the local storage usage keeps climbing relentlessly, so now I really need to make the move to S3.The guides linked here in the thread all mention migrating the cache folder. That's why I had intended to do that too. But honestly, I'm not really care about the cache. As @nebulon rightly pointed out, it'll just get repopulated anyway. Sure, that might lead to some performance hits, but that's a secondary concern.
My main concern is really the assets that are permanently stored on my instance. I can't just leave those behind. Since there's no fallback mechanism, all existing media files will inevitably result in 404 errors. Once S3 is activated, Mastodon will only look for files in the S3 storage. So, uploading everything to the S3 bucket is essential. I intended to use awscli for this, but installing it in the container following Amazon's instructions failed. It's possible I did something wrong, though. I'd be really grateful if someone could point me in the right direction here.
Thanks a lot!
Matrix: @nichu42:blueplanet.social
-
I think the thread title might have caused some confusion. I originally started this thread because I was having issues with backups. I managed to resolve those for the most part by aggressively clearing the cache, so I postponed the S3 topic.
However, my (public) instance has continued to grow since then, and some users are posting plenty of pictures and videos. As a result, the local storage usage keeps climbing relentlessly, so now I really need to make the move to S3.The guides linked here in the thread all mention migrating the cache folder. That's why I had intended to do that too. But honestly, I'm not really care about the cache. As @nebulon rightly pointed out, it'll just get repopulated anyway. Sure, that might lead to some performance hits, but that's a secondary concern.
My main concern is really the assets that are permanently stored on my instance. I can't just leave those behind. Since there's no fallback mechanism, all existing media files will inevitably result in 404 errors. Once S3 is activated, Mastodon will only look for files in the S3 storage. So, uploading everything to the S3 bucket is essential. I intended to use awscli for this, but installing it in the container following Amazon's instructions failed. It's possible I did something wrong, though. I'd be really grateful if someone could point me in the right direction here.
Thanks a lot!
@nichu42 said in Backing up media cache:
installing it in the container following Amazon's instructions failed.
please post the error or open a new thread for clarity.
-
@nichu42 said in Backing up media cache:
installing it in the container following Amazon's instructions failed.
please post the error or open a new thread for clarity.
