You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be useful to for example switch from using local storage to s3, without having to migrate existing files but having their URLs still work rather than pointing to the new asset_host
The text was updated successfully, but these errors were encountered:
For local storage the app domain is going to be used but for S3, I don't think you can serve file from your own domain unless you have additional proxies in place.
I don't mean serving s3 files under your domain, but rather when you change your config from local to s3, and users have already uploaded files, currently the URL generated changes to use the s3 hostname, resulting in 404s, whereas it should remember to use the local domain for only those old uploads.
It would be useful to for example switch from using local storage to s3, without having to migrate existing files but having their URLs still work rather than pointing to the new asset_host
The text was updated successfully, but these errors were encountered: