#django

Boogymanx: Double check the paths and permission.

oh I just thought of something

could it be because i still have the )+STATIC in my urls.py?

well that wasnt it

what permission does my folder need to have Ryan?

they're all chowned to the user running nginx

readwrite for the user accessing them

Ryan: he has that

hm

Pull up your browsers dev tools and see what urls it shows.

GET http://178.62.232.223:8000/static/images/doc.svg 404 NOT FOUND

in nginx, I have a location ~^/static/ { root /opt/yoonify/Yoonify/static/ }

which is where my static folder is

at first I had an alias there for the same location but that didn't work either

Boogymanx: maybe ask in #nginx?

Fair enough

pretty dead in #nginx

Boogymanx: can you paste your complete nginx.conf for this server{} block?

although I have to say I only just removed two slashes from location ~ ^ static

just to see if trailing slashes were the issue

oh wait

that's not what you asked

https://dpaste.de/F0mx here it is jwa

I haven't made any changes to it

Boogymanx: did you try location /static/ { ... }

I did, that's what it said first

but someone on SO said to use the ~ ^ so I tried that to see if it would work

are you sure your nginx is listening on port 8000?

not really, I was just following the DigitalOcean tutorial

how do I make sure?

hey all, has anyone ever used shopify_django_app

it is in the proxy_pass in my sites-available/yoonify

Boogymanx: that is gunicorn listening on port 8000. nginx listens on default port 80 if you don't specify anything other

Boogymanx: the idea is that you access http://mysite and nginx internally redirects to localhost:8000

Anybody here has a recommandation for a facebook api package for python? :)

Is there any thing existing to organize model logic, something like: a parent has children, if all children "are turned off", that the parent also got's turned off

*and can not turned on, like disabled

hrm...

Hi. I have an old django 1.4 project I need to run. It runs fine on my computer and currently I’m trying to set it up in a docker container. When running the same command in the docker container I get: „Error: No module named myapp.other“. („other“ is a submodule I have in this project)

What can I do to fix this ?

akamos, good question. it seems like something might exist, but i havent used it.

Why does STATIC_ROOT default to None when MEDIA_ROOT and MEDIA_URL default to an empty string?

akamos, it wouldn't be terribly hard to implement that functionality though

"Changed in Django 1.6.2"

skyrz: how I can define it? Is there anyway still in models to define?

AtomicSpark: staticfiles is a contrib app, and so shouldn't be *required*, AFAIK

Oh!

akamos, off the top of my head, I can think of a couple ways to implement it. with mixins, signals, altering get_queryset, or just stringing queries together. but ultimately it's going to revolve around some sort of boolean field on atleast one model

If it's an empty string, it spams your root directory. That's... not safe. https://code.djangoproject.com/ticket/21581

well, that ticket is marked as fixed, so?

kezabelle: Fixed awhile ago. I was just intrigued why it was different.

MEDIA_ROOT should default to None too IMHO, if we're going with that approach. I accidentally spammed my project directory with pictures earlier today.

well, that's more difficult, because Image/File fields aren't contrib

[well, that's one argument, anyway]

[I can't speak for the overall validity of the notion]

skyrz: what you mean with the boolean fields?

akamos, a boolean field is True or False, so if your field was named `turned_on` you would append to your query `turned_on=True`.

skyrz: ah yes of course, i will try to write a mixin

that way you can "turn on/off" what you wish. how you chain that up or down your relationships is where the decisions must be made

but how I make it nested? lets tell i have 4/5/6 levels

it might be safer to alter get_queryset so that stipulation is always included

akamos, there's several ways to do that. you could put a `turned_on` field on all your models with a mixin, overwrite save to turn off the rest. or you could put only one turned_off at the head/root and when you make the query, follow the query all the way up to the head/foot node. i dont know there's plenty of ways, and im just thinking off the top of my head

but i have to go to work and can't really work through the implications right now

skyrz: you still gave me good inputs, i think i can do it