On 10/27/2014 10:01 AM, Scot Hacker wrote:
>
>
> On Monday, October 27, 2014 8:58:36 AM UTC-7, Scot Hacker wrote:
>
>
> add2virtualenv /path/to/custom/apps/directory
>
>
>
> And when its time to deploy, you'll need to do similar on the server,
> using an equivalent method in the wsgi def
Hi Frankline,
On 10/27/2014 12:38 AM, Frankline wrote:
> I am having problems with my custom user model while using Django 1.7.1
> and Python 3.4.
> I have declared a Custom user model in an apps.users.AuthUser. I then
> have another application (apps.pets) that will use the AuthUser as a
> Foreig
On Monday, October 27, 2014 5:44:55 AM UTC-7, Collin Anderson wrote:
>
> Hi Frankline,
>
> Like you said, you need to use 'app_label.model_name' for AUTH_USER_MODEL,
> instead of 'apps.app_label.model_name'. Django looks at INSTALLED_APPS and
> knows to add the "apps" prefix when importing.
>
>
On Monday, October 27, 2014 8:58:36 AM UTC-7, Scot Hacker wrote:
>
>
> add2virtualenv /path/to/custom/apps/directory
>
>
>
And when its time to deploy, you'll need to do similar on the server, using
an equivalent method in the wsgi definition, e.g.:
import os, sys, site
sys.path.append('/path/
Hi Frankline,
Like you said, you need to use 'app_label.model_name' for AUTH_USER_MODEL,
instead of 'apps.app_label.model_name'. Django looks at INSTALLED_APPS and
knows to add the "apps" prefix when importing.
What's wrong with setting AUTH_USER_MODEL to 'app_label.model_name'?
Collin
--
Yo
5 matches
Mail list logo