#django

I'm thinking it's a SESSION_COOKIE_DOMAIN & CSRF_COOKIE_DOMAIN issue

what's SESSION_COOKIE_DOMAIN set to?

jamarad-p_wlb4WG

im a newfag to django how come when i add a model to model.py and syncdb no sql is generated?

Since everything works in Chrome I took a look at the cookies and this is what I see. There is one cookie for the parent domain. And that works for all of my subdomains. But in Firefox and Safari, The first subdomain I visit get's a cookie (that is somehow valid accross all of my subdomains), and the parent domain gets it's own seperate cookie.

.this.that

which is in my /etc/hosts

trick2g: Django 1.7?

trick2g: the module's normally called models.py btw

1.6.5

ya models.py

trick2g: can you share it?

In Safari & Firefox, the subdomains are fine. But the parent domain produces CSRF errors. Which are no good.

smiley: what else do i need to do to generate a new table

any idea how im setting the django module incorrectly SmileyChris

trick2g: if it's a totally new model, syncdb *should* be fine

badams: you haven't told us how you've set it, so it's difficult to guess

well, i just tried to manually set it

how?

export $DJANGO_SETTINGS_MODULE=...

no $

oh duh. i always forget that!

damn. good catch SmileyChris

smiley: do i have to add it to INSTALLED_APPS

if a field is already set on my modelform, how do I modify which widget it is using?

trick2g: is it a new app?

idk it's a new model

trick2g: the package containing the models.py shoudl be in installed_apps though, yes

sorry, all. got distracted by someone coming in here. I'll get back to this later.

ok SmileyChris: OSError: [Errno 2] No such file or directory: '/opt/lrms/envs/agency_reports/lib/python2.6/site-packages/agency_reports/assets/js'

trick2g: if it's a new model in an existing app's models.py, then syncdb should catch it

but it doesn't.

badams: and does that file exist

badams, was that in the browser?

trick2g: can you dpaste the models.py?

collectstatic maybe?

no, that was via command line, from collectstatic

riger that

roger that

ruger that

oh no

i started a trend

a trund

smileychris: http://pastebin.com/F6e2FJ5V

ugh

I wont be able to sleep now that I'm a trend setter.

:D

I'm be nervous I'm sleep wrong

trick2g: so is this going in an existing models.py

joespeakeasy: you'll never get to sluup now

Need more scotch.

smiley: yes

SmileyChris: https://gist.github.com/brjadams/009c8599bfc647...

has anyone got to the SUPER IMPORTANT WORK of solving my cookie crisis?

trick2g: does this app have a migrations directory?

drr

joespeakeasy: maybe if you stop the shouting

refresh that. goofed

maybe… hmmnnn

smiley: yes

trick2g: then that's why - it's managed with south

yep

trick2g: you'll need to create a migration for that

do i need to edit __init__.py?

always use SOUTH

never use south

always use 1.7

lo

well, then south is baked in :)

essentially.

I'm looking for implementations SESSION_COOKIE_DOMAIN on github… someone has done it correctly.

it's not south :P

it's just more awesomeness by the same author

haha. well ... true, technically

indeed.

smiley: do you know the exact method how i would do that?

joespeakeasy: so your csrf cookie domain is set to the same?

i tried schemamigration

yes sir

head scratch

trick2g: yep, that's what you want

trick2g: with --auto

I'm running my NGINX on a funny port, that wouldn't matter would it?

when i type schemamigration log --auto it says app log not found

pff, real programmers type their migrations by hand (including frozen orm :þ)

lol

or write a tool to do it, ooooooooh wait south

bdmc: sorry, just came back, did you fix your problem?

btw, admin files, do they get collected via collectstatic?

joespeakeasy: wouldn't think so

me neither...

joespeakeasy: is the csrf cookie's domain actually being set correctly

how do you mean

if there is a chance I screwed it up… that's probably the issue

joespeakeasy: what's the reason for the failing csrf validation?

django usually tells you why it fails

smileychris: it says app with label Log could not be found. what do i do?

like the logs?

logs would help, or debug mode

apollo13: separate cookie for separate domains (in firefox)

separate subdomains

I'm running logstash lemme look

yeah, I'm setting up dynamic subdomains for accounts (client1.example.com, player2.thegame.net)

one cookie for all subdomains and a separate one for parent domain

right?

but not in Chrome

correct

and we can't look at it? :(

joespeakeasy: try to drop the leading .

na, that one is required

okay

it is required though

if you want to spawn more than one domain

the sky falls when it's not there