#django

nginx is arguably easier unless you already know apache quite well, yeah

btw apache now used as reverse proxy or still with mod_wsgi too?

moldy: The question is what define functionality? It's not one app per model, it's one app per logically related models.

but apache can also serve a django app very well with 5-10 lines of config. if you know apache well, no reason not to use it.

newdimension: yes, that is a good way to structure apps then

GinFuyou: using it as proxy makes the contact surface smaller...

GinFuyou: easier to understand. very easy to run gunicorn in a screen session, for example

GinFuyou: probably easier to separate prviliges with different system users, although i /could/ be starting a rumour, there

GinFuyou: both / either [never really understood which term is the right one in english] are fine

newdimension: is your app reusable in another project? if not, it doesn't matter much, and you probably should spend your time thinking about different problems

OK, before I seen only guide where using apache == mod_wsgi

GinFuyou: mod_wsgi => apache

nah, that's obvious. I think I just got impression that apache is heavy for just a reverse proxy

only if you install mod-php ;)

apache is probably super-lightweight compared to modern hardware

anyone know why my check_image_size method isnt working? not getting any errors or traceback. My code: https://dpaste.de/o7H3

firefocks: where is it called?

the view doesnt automatically call it?

why should it?

also, what view?

fission6: how does it fail?

oh do i pass it in the model.ImageField?

a form is not a field

i mean pass the method in the model.ImageField

don't you mean clean_FOO ?

firefocks: why would anything call check_image_size? what in the docs told you adding a random method to a Form class would get it called?

ya nvm on the model.ImageField

where does it called then?

what?

if you want to add custom validation to your form ... you need to add a clean method

like you read about in the docs, right?

firefocks is somewhat right, clean_<fieldname>() is called automatically

(on full_clean())

firefocks: hence the question, _why_ do you think your method should be called?

funky bob, pretty sure i am cleaning the image field with cleaned_data.get('image', False)

hop, i guess i didnt know i had to call it manually

firefocks: you missed the actual question

if you follow the documentation you won't have to call your clean functions manually

instead, you just "made shit up" and asked why it didn't work

ok ill read it again, gotta go tho thanks for the help

If I delete all Permission objects, is there a way to have Django regenerate them? I wan to get rid of permissoins for models that don't exist anymore

last I checked django does that itself, when it removes the content-types entries for them

FunkyBob: I have migrate app zero and removed the app form INSTALLED. The permissions are still there

oh, no, that's quite different

Were you saying that it will re-add the permissions on its own?

IIRC content-types has a post-migrate hook to clean up... and permissions has one for fixups, too

You're right https://github.com/django/django/blob/b9cf764be...

Deleted all permissions, and then just ran migrations and the table got populated

I wasn't going to say "yes" without being sure... or you'd lose data [well, you lost data, but it seems youd on't care :)]

yes, I always test local first

But in general I haven't reached production yet. Hopefully soon

of course, if you delete all permissions, you delete any permissions assigned to people

Is there a way to "copy" permissions assigned a group to another? e.g. I'd set up the permissions of one group manually then copy it. I'd add/remove permissions on the new group but it'll be less work because the bulk of them are set

I guess I can loop