Directus now manages all of our assets. We use its CDN to access images directly rather than downloading and storing them in Git. Directus's CDN works well, and this greatly simplifies our configuration and makes Git simpler to work with.
Directus also has nice metadata we can use in the future, like pre-computed image dimensions so that we can better set up the page's container for the image before it has loaded.
During the migration to Directus for the database itself, we'll still upload files to Google Tables. The nightly cron job will then re-upload those files to Directus. Once the migration is complete, our cron job will solely need to get the file ID from Directus without having to deal with the blob. The migration period should handle new files correctly, but I don't think it will handle edited files, so I'll warn the team to let me know if they make any edits (which should be rare).
Directus now manages all of our assets. We use its CDN to access images directly rather than downloading and storing them in Git. Directus's CDN works well, and this greatly simplifies our configuration and makes Git simpler to work with.
Directus also has nice metadata we can use in the future, like pre-computed image dimensions so that we can better set up the page's container for the image before it has loaded.
During the migration to Directus for the database itself, we'll still upload files to Google Tables. The nightly cron job will then re-upload those files to Directus. Once the migration is complete, our cron job will solely need to get the file ID from Directus without having to deal with the blob. The migration period should handle new files correctly, but I don't think it will handle edited files, so I'll warn the team to let me know if they make any edits (which should be rare).