I’ve a considerably large amount of content in the CMS already in use. The upload_file table in the database contains the URL of the file and the provider. If I am to move all the content to S3 from Linux, and change the provider in the provider column, will it work or break? How do I deal with the formats column?
So I been working on this myself from local to S3.
So the steps you will need.
- Copy all images from server to S3
- The URL etc will still be uploads but it changes from
uploadsI THINK so might need to have a migration on the database or depending on how you consume it in the database.
The issue is, I can replace URLs, but the thumbnails in admin panel stop loading. So wondering how to make this work!
Need to extend multiple files, I been working on it a while now myself.
But like card, card preview and edit form in the uploads components needs to be extended.
I would possible wait until 4 and make a plugin with it.
Ok, thank you! I look forward to the plugin!
Well as I said, it might be.
One thing btw, I think I explained the url changes, but that’s only needed with cloud front.
If it’s just s3 I think the images can be stored a bit differently.
Any inputs on moving local to S3? Thank you!
@DMehaffy Can you please give some insights into moving media of the existing projects from local storage to the upload provider storage?
I’m guessing moving the images you can use aws cli. I mean is it on a server?
Ftp? Web interface Dowload all upload all? Are they in a docker container?
Zip all images download and upload them?
Issue is not with uploading images. I can move all images from local to AWS S3. The database for Strapi has a table ‘upload_file’. This table has columns - ‘format’, ‘url’, ‘provider’. I can modify the ‘url’ and ‘provider’ column with a query, by appending S3 link to all urls and by changing the ‘provider’ string. However, I need to fix the ‘format’ column to make the thumbnails work on CMS work. How do I do that?
Should not need to modify them
It would still store it in there as /uploads/ etc for the S3 bucket or uploads/
The provider and format I think is internally for Strapi to use, or info itself not how it’s rendered.
Strapi itself will prefix the URL with the backend etc, unless you want to extend files using cloud URL
I had to rewrite at work to use cloudurl when this was enabled. But for normal Uploads for S3 it should work just fine.
I know that this is old, but I am having the same issue where I host the uploaded images in an S3 bucket, and use a PostgreSQL database. URLs in the
upload_file table are the absolute URLs, and they contain the bucket URL as a prefix. My issue is that I want to move the images to a new bucket with a different URL. Simply changing the configuration of Strapi will only change the URL for the new uploads (Correct me on this if I am wrong), but won’t change the pre-existing images’ URLs. How do I change the existing images’ URL to be prefixed with the new bucket URL?
My current approach is:
- Move the images to a new bucket
- Configure Strapi to upload on the new bucket
- Use SQL queries to modify the
formatscolumns in the
Is there any better way to do this?
I’m also facing the same issue while migrating assets to s3, is there any better approach to change the URL of already existing media files?