Backing up media cache
-
@nebulon Thank you for your reply. In the instructions it says that first you have to run the command
cd /home/mastodon/live aws s3 sync --acl public-read public/system/ s3://instance-media --endpoint=https://s3.fr-par.scw.cloudTo synchronize local data, cache Mastodon media to the S3 bucket.
I guess that would have to be a different command here on Cloudron.
Now my images load, but the local avatars, server image have disappeared from the instance and the remote images and avatars are not loading. Is it possible that the remote images will load gradually, I don't know.
I've been really struggling with this for a few days now and the result is still not good.
-
Hello
Did you finally succeed to synchronize your local data ?
I've the same issue, no more avatar for example -
@doodlemania2 Could you please elaborate a bit more on how you managed to get awscli working inside the Cloudron container? I'm having trouble installing it (getting "file system is read-only" errors all the way long).
-
Not sure if including this in the app image is a good way forward. Trying to understand what the issue here is in the first place. So you want to move the media cache from mastodon to a S3 bucket? Is there any reason to sync this via S3 tooling instead of setting up the bucket in mastodon and then just let mastodon deal with cache misses?
-
Let me say that moving ANYTHING from a media cache to another S3 bucket is just an exercise in frustration. Listen, I know modern software promises that everything will work, but it just doesn't sometimes. I also have done this dance with Mastodon, and in the end the ONLY thing that works is me saving my original media which I use on my own instance, locally. When I move the instance, I just refer to a screenshot of what my Mastodon looked like, and use the same image files for logo and icon and etc. Trying to get x number of weeks, or even months, of accessed media to transfer over???? Forget about it. Really. It's just not guaranteed. If you are going to move your instance, download your followers, download your personal media, download your hashtags, moderation list, etc., EVERYTHING, and when you are finished setting up your new instances, reupload everything. Inconvenient? Sure. "But mastodon said it should work!" - but it doesn't. I think the reason I accept it and just work around it is because I am the one still in charge of my media. It is my privilege to download my info, save it, and be able to use it again.
But transferring over a cache?? Why? I tried, too, but as I observed the nature of Mastodon, why would I expect that to even be possible? The toots I like, I save. The links that caught my eye, I followed and saved with my ArchiveBox. The toots go flying by, and in a week there's simply been too many.
-
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!
-
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.
