One approach I am looking into is adding / overiding the static template 
context processor. But I am wondering if there is a cleaner way. Or 
something simple that I am overlooking. 

On Friday, November 20, 2015 at 4:48:28 PM UTC-8, Matt Mansour wrote:
>
> Howdy all -
>
> I am working on multi tenancy mezzanine project. I define a static URL in 
> settings (in this case a Cloudfront URL). However, the static URL needs to 
> change to match the site I am accessing. 
>
> For example, if I am on *example.com <http://example.com>* I want my 
> static url to render as *media.example.com/static/ 
> <http://media.example.com/static/>... * Likewise, if I am on *example2.com 
> <http://example2.com>* I want my static url to render as 
> *media.example2.com/static/ 
> <http://media.example2.com/static/>*
>
> Has anyone here had to implement something similar? 
>
> Unfortunately when images are rendered from a different domains than the 
> site domain strange things can happen; like Facebook share reach 
> diminishing, as their current algo seems to associate that sort of thing as 
> spam.
>
> Cheers
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to