Use Custom Domains

[alpha1]

While it is awesome to use the domain awesomeness.openphoto.me, would it be possible to use the real domain, either user.trovebox.com or usersdomain.com when pulling and linking images from trovebox. This would make it less dependent on trovebox as a service.

[jmathai]

Long running issue. I think the real problem is that the frontend doesn't proxy requests to static photos. We always return URLs directly to the photo (an S3 URL in this case).

I reopened photo/frontend#401 which was tracking this.

[alpha1]

Wonder if we could "rewrite" using the saved openphoto site setting?
Those images are really stored at S3, even if image was uploaded to dropbox or box?

[jmathai]

Each storage adapter is different. For Dropbox and Box we don't store thumbnails on those services. Mainly because they don't operate as well as a CDN. Loading thumbnails would be significantly slower than loading from somewhere more suited for CDN type requests.

That being said, if you'd really like to have thumbnails stored on a different domain that's doable too by using your own S3 for the thumbnails, instead of using the bucket we provide.

Sorta long winded but hope that makes sense.

If we proxy the requests that solves the problem since the URL would be to your site URL (custom domain or *.trovebox.com) and we'd seamlessly proxy the thumbnail from wherever the source is. This does add a little bit of latency, fyi.

[alpha1]

Very interesting. Thanks for the explanation.