- Notifications
You must be signed in to change notification settings - Fork1
saeidee/s3-to-cloudinary
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
It is an implementation of migrating all of your media from S3 to Cloudinary, using goroutines it has the highest performance
You need to enable lazy loading and map your buckets in your Cloudinary dashboard you can find more information about lazy migration herehttps://cloudinary.com/documentation/fetch_remote_images#auto_upload_remote_files.
After that update your keys in the config.yml and then since this project is a CLI tool, so you can run the start command to start migration. By default, it is listing 25 bucket object per request you can increase it from config.yml file, aws has limits up to 1000 keys per request.
foo@bar:~$go run trek.go start
After migration finished, you will have an Excel log file called s3-to-cloudinary-logs.xlsx, you can see the errors, total assets and total sizesuploads.
- Richard Bajuzik