On 1/10/2010 11:48, bruno desthuilliers wrote:
> This is fine when using the dev server, but what when you will serve
> your static files directly from the frontend web server ?
Hi Bruno,
to answer your question, i'll post the relevant parts of configs.
I use apache with the wsgi module, nginx f
>> I'm developing on Windows so i don't have the luxury of a nicely working
>> symlink system :)
>
> ??? Windows is STILL not able to properly handle symlinks ???
>
> OMG :(
mklink might work. Didn`t know of this myself before I googled
"symlinks in windows":
http://lifehacker.com/5496652/how-to-
On 1 oct, 10:55, Benedict Verheyen
wrote:
> I found a solution that works for me.
> In the application dir, i've made a media\calltracking directory where
> the static files go.
> I need the extra dirname in the path (the trailing calltracking), otherwise
> i end up with media not being found.
F
On 1/10/2010 10:06, bruno desthuilliers wrote:
> I don't think that's the case, and FWIW the OP's layout makes perfect
> sense to me. His point is that even while all apps are in a same
> project and share a common auth, they are otherwise totally (or
> mostly ?) independent so it doesn't really ma
> FWIW, even for a more canonical "integrated" website / webapp composed
> of distinct django apps, "assets" (app specific css, js, images and
> whatnot) management can sometimes be a pain. My own solution so far is
> to keep all app-specific static stuff in a /medias/ subir of
> the app and manual
On Fri, Oct 1, 2010 at 10:06 AM, bruno desthuilliers
wrote:
> On 30 sep, 22:45, Carles Barrobés wrote:
>> If the ideal solution for you is different sites, one authentication,
>
> I don't think that's the case, and FWIW the OP's layout makes perfect
> sense to me. His point is that even while all
On 30 sep, 22:45, Carles Barrobés wrote:
> If the ideal solution for you is different sites, one authentication,
I don't think that's the case, and FWIW the OP's layout makes perfect
sense to me. His point is that even while all apps are in a same
project and share a common auth, they are otherwi
If the ideal solution for you is different sites, one authentication,
I found a reference in...
http://stackoverflow.com/questions/556907/how-to-get-distinct-django-apps-on-same-subdomain-to-share-session-cookie
...pointing to a "django-cas" application that is meant for that
purpose (Single Sign-
On 29/09/2010 18:55, Carles Barrobés wrote:
> At some point I also thought this was a good idea. This way I can
> reuse the app and all its visual stuff as well.
>
> But the problem is that for most cases you will want your templates
> and media to be consistent with a site's design and look&feel.
On 29/09/2010 13:58, Benedict Verheyen wrote:
> On 29/09/2010 13:13, David De La Harpe Golden wrote:
>> On 29/09/10 09:34, Benedict Verheyen wrote:
>>
>>> In my template i add this:
>>> >> href="{{MEDIA_URL_CALLTRACKING}}/style/login.css" />
>>>
>>
>> (I'd favour prefix rather than suffix if you're
At some point I also thought this was a good idea. This way I can
reuse the app and all its visual stuff as well.
But the problem is that for most cases you will want your templates
and media to be consistent with a site's design and look&feel. This
means that for two projects (sites) re-using the
On 29/09/2010 13:13, David De La Harpe Golden wrote:
> On 29/09/10 09:34, Benedict Verheyen wrote:
>
>> In my template i add this:
>> > href="{{MEDIA_URL_CALLTRACKING}}/style/login.css" />
>>
>
> (I'd favour prefix rather than suffix if you're going to pseudo-namespace)
>
> Did you introduce suc
On 29/09/10 09:34, Benedict Verheyen wrote:
> In my template i add this:
> href="{{MEDIA_URL_CALLTRACKING}}/style/login.css" />
>
(I'd favour prefix rather than suffix if you're going to pseudo-namespace)
Did you introduce such a MEDIA_URL_CALLTRACKING variable into the
template context by any
13 matches
Mail list logo
