#Idrive mansfield how to#
Follow the previous post I linked to in the beginning for instructions on how to set up Mastodon with Docker. Of course you need to configure the other settings for iDrive. The last bit is setting the S3_ALIAS_HOST environment variable for Mastodon to the hostname, with your custom domain instead of iDrive's endpoint. It will take a little while and several attempts depending on DNS propagation, but eventually it should add the CNAME correctly. TLS certificate: enter the certificate and the private key you generated with Cloudflare.Ĭonfirm. CNAME: use the wildcard domain, in my case it was *.botta.social Click on "Add CNAME", then fill in this way: This will open a panel on the right side. Next, go your iDrive account, and click on the "Settings" button under the region of your bucket. Click "OK", then enable the toggle under "Authenticated Origin Pulls". You will be presented with the "Origin Certificate" as well as a "Private Key". You'll need to add both the root domain and the wildcard domain, so for me it was botta.social and *.botta.social. Next, while still in Cloudflare, head to the SSL/TLS tab > "Origin Server" and click on "Create Certificate". So now you should have a CNAME record for *. pointing to whatever endpoint iDrive has assigned to you for the region you have enabled. So in my case the bucket is named files because I use the subdomain to serve my Mastodon assets.
Like I said earlier, for this to work correctly you should have given the bucket the same name that you want to use as subdomain. Once you have added the domain, go to the DNS tab in Cloudflare and add a wildcard CNAME record pointing to your iDrive e2 endpoint. This means that hereinafter you will be using Cloudflare as nameservers for your domain. If you don't use Cloudflare yet, create an account and follow the simple instructions to add your domain to Cloudflare. This is the part that requires a bit more steps.
#Idrive mansfield install#
Documentation about iDrive e2 is still not great, but luckily I found that it supports S3 bucket policies, so that's what I recommend you do.įirst, you need to install the AWS CLI on your computer and configure credentials (see docs in the link) then create a file somewhere (say /tmp/policy.json) with the following content: What you want to do instead, is to configure a bucket policy that only allows public reads, while requiring authentication and authorization for any other action. This makes the bucket public for both reads and writes, meaning that third parties would also be able to modify the content of your bucket, which is probably not what you want.
Upon request (for now, but they are going to make this possible in the control panel soon), they can make your bucket public, but don't do that. I should mention that it is possible to solve the problem with public URLs mentioned earlier by contacting support. So temporarily I used a simple Nginx container as a proxy in front of the bucket and that worked.Īfter spending some more time on it and also with some help from iDrive's support (which gave me good first impressions btw), I managed to get iDrive e2 working properly with Mastodon without a proxy container and behind Cloudflare, so I don't have to worry about egress bandwidth (iDrive e2, like Wasabi, has some limitations in this regard). Also iDrive is a company with a long experience with storage services like backup, so it should be reliable as well.Īt first, however, I couldn't get an iDrive e2 bucket to work with Mastodon out of the box because the files must be readable with public, non expiring URLs, and this was not possible with this new object storage service. I haven't done any benchmarks or other measurements but iDrive e2 seems even faster than Wasabi. So I opened an account and I was impressed right away by the control panel but also the performance of the bucket operations. I am not aware of a cheaper object storage service compatible with the S3 API. After 1 year it's $40/year, which is still cheaper than Wasabi. There is still an introductory offer for 1 whole Terabyte for just $4 for the first year, which is awesome. Wasabi is an awesome service, pretty fast and reliable, but I came across a newer service called iDrive e2 which is even cheaper and since Mastodon can use a lot of storage, I decided to try it. When I first set up my personal Mastodon instance ( here's how I did it and here is a follow up on how to set up a crossposter between Mastodon and Twitter), I used a Wasabi bucket to store my instance's media and assets.
0 kommentar(er)
