#django

i mean it transforms relative paths to absolute

sorry, i should have said it clearer

mattmcc: you might wanna take to ansii

anssi*

uffs: so where is the static file?

also, are you in debug mode etc…

i am in debug mode, the static file is in {PROJECT_ROOT}/static/test.js

apollo13: Yeah. It's actually been an issue for me for over a year; even had an email draft to Malcolm that I never sent because it didn't feel substantial enough at the time. :P

uffs: stuff in PROJECT_ROOT/static isn't picked up magically

I love typos in my templates. especially the one that excludes the analytics script code in production. ;/

your settings never reference PROJECT_ROOT/static as source for staticfiles

jcockhren: users block it anyways, so…

I believe STATIC_ROOT = j('static') does

def j(*args):

return os.path.join(os.path.dirname(os.path.realpath(__file__)), '..', *args)

uffs: no it doesn't -- STATIC_ROOT is ment for collectstatic

this is where all files will end up, but not where to search for them

ok, so how do i make it search for them in there?

it won't let me add it to STATICFILES_DIRS

I doubt that

Well, if it's a tuple..

swear on me mum

"The STATICFILES_DIRS setting should "

ImproperlyConfigured: The STATICFILES_DIRS setting should not contain the STATIC_ROOT setting

yes

Oh, yeah, you don't want to do that.

cause STATIC_ROOT should be something else

oh well

you can't load and write staticfiles to the same dir

The whole point of STATIC_ROOT is that it's disposable. Nothing lives there.

now i am perplexed

you might wanna read the staticfiles docs, especially on collectstatic to understand the difference between those two

why does django-pipeline writes it there then?

Because it's the place that your production server serves static files from.

i guess i am not supposed to be using it in debug, alright

in debug STATIC_ROOT is never touched

Right. In development, the idea is that you use the sources.

files are served directly there from the finders

bad idea, but well…

(not so bad idea actually, but has some implications :()

yeah, that's great, but how do i test it?

test what

i want to make sure django-pipeline minifies everything all right and treats less and all other special files properly

I never used pipeline, sry

uffs: i use pipeline as well. one sec. let me grab a config

ok. even during testing where DEBUG=True

STATICFILES_DIR is traversed when running collectstatic

and placed in STATIC_ROOT

you can have the dev server 'serve' the static files

alright, thanks everyone

log story short. use absolutes

the "output_filename" for the pipeline will be placed in the static root

uffs: https://docs.djangoproject.com/en/dev/ref/contr...

jcockhren: thanks

jcockhren: psst... don't like to dev docs!

for me, that site always defaults to dev

Google has an annoying habit of indexing dev docs higher than release docs.

Hi guys, I'm looking for the easiest way to start gunicorn running under SSL. Do you guys know a tutorial that walks me through it?

the_drow: people typically have something running in front of gunicorn

I for example, use nginx+SSL in front of gunicorn

jcockhren: I'm using this for quick and dirty integration testing (locally. yes, I know it's not really integration testing but that's the best I can do for now)

Gunicorn has SSL support. I just need a tutorial for how to generate the keys correctly and make Django work with it.

Where should I store these if I am using gunicorn?

put them whereever

Got it.