Gregory's Server@webology images were by far the worst part of this - my process sucked: I took a photo on my phone, waited for iCloud to sync the photo to my Mac, dragged that photo out to convert it to JPEG, then dropped that onto https://tools.simonwillison.net/image-resize-quality to grab a smaller file size version, then dragged THAT to Transmit to upload to my S3 bucket, then manually entered the img tag in the HTML of a live blog update
|
8 comments
 @simon I realized while microwaving my lunch that it would take about as much time to have Claude build me a file upload tool for my project changelogs (blogs) than it did to ask you how you solved the problem. One model + one upload form and one list view with a clipboard snippet that gives me a markdown link was what I think I needed. This technology is such a light bulb moment. Once we automate the git and pr parts we will soon be chatting with our repos to add features.  @webology I think I need to get over my resistance to having Django handle file uploads and forward them on to S3 - I've always preferred having my browser push content to S3 directly, but maybe in 2024 the servers I'm running apps on can handle proxying a few MBs without me need to worry about running out of server resources @webology I still love this 14 year old Django snippet https://djangosnippets.org/snippets/1868/ @simon we really need to promote that website more. 8 months is too long to go since the last snippet. @simon @webology why don't just use Django Storages? It's "transparent" and you can change your storage provider in the future without any vendor lockin effect 👍 |
@webology I got half way through building a dedicated mobile web app for taking a photo on my phone and resizing that and uploading it to my S3 bucket, but I couldn't get S3 CORS headers to work right so I gave up