how to point URL to an s3 bucket after generation? about nuxt-image-loader-module HOT 2 OPEN

Hi Simon,

Thanks for raising this issue and for your kind words.

S3 integration isn't something that I've tested so far. I can add this to the roadmap for this plugin, although I can't immediately put my attention on this due to busy work commitments.

I think S3 integration would be a worthy addition and as you have a real use case, I'd like to ask you a few questions so that I understand what you're trying to achieve.

Are you trying to:

• Put your entire compiled nuxt app on S3 and host from there
• Retrieve existing source images from an S3 bucket?
• Point the compiled <img> sources to a remote S3 bucket where the compiled images live?
• Is you S3 bucket publicly accessible - i.e. no access permissions set?

I'd like to see if there is a general solution that's not necessarily S3 specific so this module can support other image hosting solutions.

Thanks,

Barry

from nuxt-image-loader-module.

Thanks Barry!

I’m not well versed in best practices for asset storage – so I was posing a question about how would be best to handle this as much as anything.

I am hosting my app from Netlify currently, and had thought it would be nice to store all image assets on a separate s3 bucket, attached to a subdomain e.g. assets.my-domain.com

Given this idea, I had thought it would be nice if during the build / generation process, assets could be generated and then uploaded to this bucket – with links amended appropriately.

With this in mind, I think my objective is as you describe in your third point:

• Point the compiled <img> sources to a remote S3 bucket where the compiled images live?

The assets could certainly be made public if necessary or easier!

Thanks,

Simon

from nuxt-image-loader-module.