#django

Yes.

The only problems I see is after a user is created I'd have to update /etc/aliases and reload dovecot and postfix

Why do you need a system user at all?

Postgres users are not bound to system users.

because I think passwd is pretty solid authentication

Oh, is this a roll-your-own cpanel clone kind of situation?

just the email part I suppose

Ideally I'd like to make a cpanel sorta system that is pluggable django apps

Surely the email server in question can auth against a database table without needing a system user.

yeah it can. But I don't see a downside to using a system user for now.

Requires root, which requires great care to do safely.

schinkel: now that I have the SMT error fixed I can see the following: http://127.0.0.1:8000 uidb64=MQ token=46f-bd6f24df22d0e6800f04 %}

Obviously I forgot to remove the %} but that's fine for now. I suppose

I got other stuff to work on tonight. But I just wanted to run it passed people here.

mattmcc, if you were going to make a role-your-own-cpanel system how would you do email?

Heh. Well, _I_ wouldn't do either of those things. But I'd be sure to use a mail server that could manage users and their mail entirely in the DB. Pretty sure Dovecot supports that.

good to know. I have this problem at work where I have zero time for planning and usually have to just make stuff work immediately.

Google Apps ftw

my boss is voting for Trump and wears a tin foil hat at the mention of Google

Managing email is just too annoying to justify doing it in-house, imho when you can spend $5/mo/user and have it all done for you, plus the apps.

Does he trust Microsoft any more? They offer basically the same thing these days.

Rackspace also does just mail hosting, $2/user/mo

My company was once a paying google apps user. Abysmal support.

but I suppose it's still a good bang for the buck

Never actually needed to use their support before.

We're kinda lucky in that we're grandfathered in to when it was still free. So as long as we stay under the overall disk quota and user count, we're good.

I'm interested to know if there is a best practice for django as far as having a BooleanField to specify whether a certain object should have a ForeignKey or whether the ForeignKey being null is sufficient.

Something like a BooleanField "has_a_favorite" and then a ForeignKey on the favorite.

I would prefer having a nullable foreign key

Should I use a null ForeignKey to represent that the user does not have a favorite

that is what I would do

I'm trying to imagine if there would be any issues with that. I guess the only potential issue is if later on I would rather have null represent something else.

null logically means "this thing does not exist"

if you are using it to mean anything else, I'd say that's somewhat confusing

jessamynsmith: Agreed. I guess that answers the question.

jessamynsmith: Thanks

cheers

Hey, has anyone had possitive expirience with https://github.com/jrief/django-websocket-redis?

hi everyone

hi

someone have ever used ModelAdmin for 2 differents database, i have a problem with delete_model function because I overwrite it and ModelAdmin Ignore it