Here's the command I used, which syncs a local folder in my computer to the S3 bucket while setting the policy to public. Since all these Object Storage providers support the Amazon S3 API you can make use of AWS's CLI to do all the hard work for you. Now that you have all your assets on your machine (zip file), it's time to upload them to the new provider. S3_BUCKET=your-bucket-name Code language: JavaScript ( javascript )īy doing this all new avatars and headers fetched by Mastodon from this point on started being uploaded to the new bucket. ⚠️ There's a difference on how to set the S3 configuration on your Mastodon instance for Scaleway, here's how it should look like (you may change nl-ams for your bucket region): S3_ENDPOINT=https: //s3. While waiting for the zip to be generated with the existing assets I updated ~/live/.env.production with the new values from the Scaleway bucket (as well as the new API credentials generated within Scaleway, so Mastodon can upload objects) ( More on this here). Since I'm a single private instance I could this step now. Mine was about 50Gb and took around 5 hours. It might take a few hours to generate depending on your bucket size, though. Create a snapshot of the bucketįrom B2 you can create a zip (snapshot), then you just download it. Want to know how I migrated? Here's how: 1. In hindsight, I should've known this when I signed up for Backblaze So the actual S3 Object Storage cost was being inflated by my bank's fees. My credit card is linked to an Spanish bank and they charge me a fee for every purchase I do in currencies other than EUR.
I wanted to highlight why and how I did it, which is trivial when you know what to do Why? Now I'm moving away from Backblaze B2 as a S3 provider to Scaleway. I eventually moved all the assets to an S3 compatible Object Storage. After starting to host my own private Mastodon instance it became clear that disk usage was going to be problem.
0 kommentar(er)
