@kevin Yes please! I've been following the cybrespace instructions, but I ran into a URL caveat.

Though it might because I am using DigitalOcean Spaces (S3-compliant).

The guide I am using: https://github.com/cybrespace/cybrespace-meta/blob/master/s3.md

@Alex oh that's the exact guide I used!

What URL caveat have you run into?

@kevin After migrating all my data, I found that the files are expected to be stored in

'bucket.region.digitaloceanspaces.com/bucket'

instead of just

'bucket.region.digitaloceanspaces.com'

No idea why, but moving all 150k files one directory deeper kept failing, so I restored from the snapshot I took before I made changes, and plan to start over from scratch with that caveat in mind.

@Alex Mine are not under bucket.region.aws.com/bucket, they're in the root folder.

I used the single s3cmd in the cybrespace instructions and didn't try to create multiple threads processing the copy

@kevin Weird... I wonder why I had different results?

@Alex No idea. Is the Mastodon app actually seeking them in the /bucket/ structure and 404ing?

@Alex though I see you're on 3.4.7, and I'm on 4.0.0rc2, maybe that's another difference

@kevin Yeah, I migrated all my files to the root the way the docs said to, and after changing my config and restarting the service, all the images were broken because they contained the bucket name as the parent folder.

Doing a right-click, Open Image, and removing the bucket name from the directory tree took me to the appropriate files.

My next worry is that new files are going to end up in the root and further break things when I try again.

@Alex very odd. There's nowhere in the instructions where it says to add in the bucket name as a folder, so I wonder if it's an app thing? Maybe it's coded in the ruby.

@Alex Don't know if you're still working on this - I found a bug report identical to yours on Github: https://github.com/mastodon/mastodon/issues/20347

@kevin nice! Thanks!

I've migrated to S3 for simplicity. Might give Spaces another go sometime in the future if the flat pricing ends up more attractive than AWS pricing.

Glad to understand how to Alias. Plan to use my own domain eventually, so I'll need it.

@Alex That may be a difference with the DO spaces, perhaps. I used AWS of course, because I wanted to try using it...maybe that's the difference

@Alex I am also on DigitalOcean but I'm on a droplet.

@kevin Yeah, my server is the smallest compatible droplet, and instead of splitting Compute and Storage between DO and AWS, I figured I'd store it all in the same datacenter.