Open mciszczon opened 7 months ago
region
is only supposed to be present when using AWS endpoint I think.
Also, when I tried to install the adapter into the /content/adapters/storage/s3 as instructed, it wouldn't get picked up by Ghost on startup. It worked, hovewer, when I installed it into /current/core/server/adapters/storage/s3—not sure why.
I don't recognize /current/core/server/
part of the path though. Where did you get the idea of this?
I don't recognize
/current/core/server/
part of the path though. Where did you get the idea of this?
current
is just a symlink to the currently installed version of Ghost.
Hi there! Thanks for forking the original adapter and maintaining it.
I have a Ghost blog on DigitalOcean and wanted to connect it with its Spaces for storage. After some tinkering I finally adapted the installation instructions and wanted to share it for anyone (myself included) in the future. If you're interested in adding it to the README file, I can make a quick PR for that.
Here's what worked for me:
Not sure if the
region
param is required though, so I added it for the sake of explicitness. One tricky part is that theendpoint
param has to have the bucket name omited, as it is added automatically from thebucket
param. I did not check if it would work by adding the bucket name straight into theendpoint
URL and just removing thebucket
param from the config.Also, when I tried to install the adapter into the
/content/adapters/storage/s3
as instructed, it wouldn't get picked up by Ghost on startup. It worked, hovewer, when I installed it into/current/core/server/adapters/storage/s3
—not sure why.Node:
v18.19.0
Ghost-CLI:1.25.3
Ghost:5.76.0 (at /var/www/ghost)