[Plugin: W3 Total Cache] Using W3TC with non-Amazon CDN which is fully compliant with the S3 API
I’m looking for a simple solution for using the CDN option with a non-Amazon solution which, however, is fully compatible with the S3 API.
DreamHost is launching DreamObjects, which fully supports both the S3 and RackSpace (Swift) APIs. However, there seems to be no simple way to get W3TC to recognise a different, S3-compliant endpoint than Amazon’s own.
What I’ve seen so far is that each time a new CDN becomes popular, W3 Edge launches a new option on the CDN configuration page. That’s great, but it could be even greater if it allows certain common APIs (S3 is probably the most popular among those) to be used with different endpoints.
Short of hacking the code and replacing the call for Amazon with the domain name for DreamObject’s API endpoint, is there a simpler way to do that?
I suppose that using the CDN via FTP might, for now, do the trick (even though I don’t know yet if that works as expected or not — I haven’t tried), but it will lose the richness of using S3’s API for uploading/updating content on the CDN.
I think that all that is needed is a box with the endpoint API server, defaulting to Amazon’s S3 (or RackSpace’s), but being editable (so that I can change it to objects.dreamhost.com, in my case). That would be awesome! More and more CDN providers are relying on open source software like Ceph which exposes a fully compliant S3 or Swift API — it makes sense to easily change just the server name to take advantage of all those CDNs, instead of waiting until W3 Edge to add yet another option on the list of supported CDNs…
Or am I totally missing the point here? Perhaps this is already possible on a “hidden” option somewhere?
Thanks in advance for any input.
- The topic ‘[Plugin: W3 Total Cache] Using W3TC with non-Amazon CDN which is fully compliant with the S3 API’ is closed to new replies.