Running Ghost 6 in a Digital Ocean droplet. I write my posts in markdown locally and then paste them into the Ghost editor, which works really well. While I am writing, I store any images I want to reference in an S3 bucket and link to them using standard markdown: !(url in here)
However, I recently noticed that Ghost slurps in those images and then hosts them locally on my bucket, which is not the behavior I want – both for portability and for offloading the work and storage to the S3 bucket. You can see an example of this on this post.
Is there a way to get Ghost to respect the canonical location of my images?
I do see some are uploaded to s3 and some are uploaded locally.
To mitigate this on my hosting, I have a patch that’s run locally but it’s really deep and complicated and not something that can be copy and pasted to work. It’s what my entire infrastructure runs on, but with R2 buckets.
So you’re not using the gallery function at all? Strictly markdown?
I want to suggest try using html and placing it in an HTML block instead as a workaround?
Thanks for your quick replies and patience as I worked through this in my latest post. In turns out the answer was user error…I think on the first post I linked I just ended up making some edits in the Ghost editor in the final editing stages. In this post, everything worked as expected with the images linking out to my S3 storage bucket.
