[03:29] <kees> mhall119: so, I'm finally trying understand this summit layout, and I'm seriously lost. I'm used to django with apps. in summit's case, the apps are "schedule", "sponsor" and "common".
[03:30] <kees> mhall119: I don't understand at all how the _website directories come into play, and how the models get loaded
[03:53] <kees> ah-ha! I see now -- the alternate settings file causes the _website dir to get added as an app! and my models weren't in admin because there was no admin.py
[03:53] <kees> I'm starting to feel less insane now :)
[04:33] <kees> yay, got some models happily working
[09:22] <daker> kees: yes
[09:24] <daker> https://docs.djangoproject.com/en/dev/ref/contrib/admin/
[09:24] <daker> and you need to pay attention about which django version you are using
[09:24] <daker> in prod/dev
[15:11] <kees> daker: yeah, the docs are good. I was just seriously confused about where things were living in the directory structure. now I just have to figure out how to populate a form.
[15:12] <daker> kees: which version are you using ?
[15:13] <kees> 1.4.5
[15:13] <daker> maybe start with the tutorial here https://docs.djangoproject.com/en/1.4/intro/tutorial01/ ?
[15:14] <daker> https://docs.djangoproject.com/en/1.4/intro/tutorial02/
[15:14] <daker> https://docs.djangoproject.com/en/1.4/intro/tutorial03/
[15:14] <daker> https://docs.djangoproject.com/en/1.4/intro/tutorial04/
[15:15] <daker> the tutorial does cover almost everything you need to get started
[15:15] <daker> models/urls/views/forms/admin
[17:50] <kees> daker: yeah, I've gone through all that. I'm going to re-read the forms bit again.
[20:50] <slangasek> kees: hmm. 'debconf_website_userprofile.sex_id may not be NULL'?
[20:50] <slangasek> (http://virgil.dodds.net:8000/debconf14/registration/)
[23:10] <daker> you need to set the sex field
[23:11] <daker> because you didn't set blank=True, null=True in your model, that's for sure if the field is optional :)
[23:24] <kees> slangasek: you need to run the "migrate" manage.py command to build the db itself, and even then what I checked in doesn't work yet since it gets angry about empty fields and such.
[23:24] <kees> slangasek: haven't had time yet today to continue, but I checked in everything I had last night (include the "loaddata" fixtures for populating the drop-downs)
[23:25] <kees> *including
[23:25] <slangasek> kees: right, I get this error even after the loaddata runs; basically the form doesn't load for someone who doesn't already have a userprofile record, AIUI
[23:28] <kees> right, I haven't figured out how to prompt for "new" data yet. ran out of time.
[23:29]  * slangasek nods
[23:43] <daker> slangasek: kees do you need help :)
[23:58] <slangasek> daker: oh, probably, but unless you want to write the django views for us we probably have to muddle through :)
[23:58] <slangasek> kees: fwiw I think schedule/views.py gives a better example, for the existing registration form