/css/css.php/file.css …which rewrites
And guess what, it all works. I had some bad experiences with the S3Fox firefox plugin in the past, but it’s since been updated and I’ve been using it regularly.
Also, using S3.php, all profile images now go directly onto images.beeets.com. Wicked.
So what does this mean? A few things:
1. Less bandwidth & work – beeets will spend more time serving HTML, CSS, and JS than images.
2. Safer – We were backing up profile images to S3 indirectly before, but the chances of S3 going down VS our hosting are slim.
3. Worse image caching – Before, I had .htaccess controlling all the caching for static files. I liked it that way. S3 doesn’t do this very well at all. Apparently it’s configurable, but I don’t know how…any ideas?
All in all, it should be better for beeets. Maybe we’ll actually let users have images bigger than 10×10 now ;)
Thumbs up to S3 (and probably all other Amazon web services).