OperationalError at /accounts/(login|signup)/ fe_sendauth: no password supplied about cookiecutter-django HOT 13 CLOSED

Hey, I am coming to this issue cause I've got the same error.

After installing some postgresql/django/python stuff with this command:

sudo apt-get install libpq-dev python-dev postgresql postgresql-contrib

I logged into the postgres user with:

sudo su; su postgres

So I could create a project specific database user with:

postgres@x: createuser -d -e -P your-dbuser-name

(and entering your-dbuser-pwd)

Then you can run the postgres commands with this user and should create the database:
createdb -U your-dbuser-name your-db-name

After that postgres specific stuff, you can change your database settings in django:

# DATABASE CONFIGURATION
# See: https://docs.djangoproject.com/en/dev/ref/settings/#databases
DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.postgresql_psycopg2',
        'NAME': 'your-db-name',
        'USER': 'your-dbuser-name',
        'PASSWORD': 'your-dbuser-pwd',
        'HOST': '127.0.0.1',
        'PORT': '5432',
    }
}
# END DATABASE CONFIGURATION

After doing all this stuff, you should run commands like:

python manage.py runserver

ps: (I have to run python manage.py migrate, perhabs you have to do the same.)
(setup: xubuntu 14.04, cookiecutter==0.7.2, python==3.4, Django==1.7 )

I hope this helps someone. ;)
br
rm

from cookiecutter-django.

closing this now as appropriate instruction has been add to README. Thanks everyone for your love, report and support :)

This serves as a doc for anyone coming from google!

from cookiecutter-django.

This is user error. Sorry.

from cookiecutter-django.

Is the user error something that could happen again? Is there a warning message we should put somewhere if someone forgets a config value?

from cookiecutter-django.

I figured out you were using Django-Configuration, and it looked like you
were injecting all your settings with environment variables, it would be
great if the README included a list of all the environment variables it
expects/requires to be set. Django-Configuration's docs are not the most
friendly. I actually ended up stripping django-configuration out since I
couldn't figure out how to use it, or an easy way to determine all the env
variables that needed to be injected. I went back to the TSoD (and my own)
layout of base/dev/prod "settings" files. Though if I could ever figure out
how to use django-configuration, it looks nice!

While this specific message I found out is related to the lack of
credentials for Postgresql, I ran into another problem with deploying to
Heroku (again, missing env variables).

I realize this is a very opinionated project. It simply isn't for me and I
respect that.

On Thu, Oct 24, 2013 at 7:34 AM, Daniel Greenfeld
[email protected]:

Is the user error something that could happen again? Is there a warning
message we should put somewhere if someone forgets a config value?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/35#issuecomment-26997296
.

from cookiecutter-django.

Welp, you've given a great account of some things that need to be fixed. Thanks for this incredible input!

Reopening so it's on my radar. 😄

from cookiecutter-django.

I'd also second this request. Just tried following the README and I encountered an error:

django.db.utils.OperationalError: fe_sendauth: no password supplied

I know it's probably due to me missing some DB username/password environment variable, but it isn't explained how was this configuration envisioned - should I pass it everytime as a --settings=local_settings or define an .env file and run the app with foreman or honcho? How is this set up in Vagrant for quick development? As this is an opinionated cookiecutter, I'd love to get an opinion for this part as well :)

from cookiecutter-django.

I've just tried using Cookiecutter for the first time, followed the instructions and get the same error upon executing the "runserver" command: django.db.utils.OperationalError: fe_sendauth: no password supplied

from cookiecutter-django.

Can you provide your OS, python version, and which version of Django?

from cookiecutter-django.

Ubuntu 14.04, Python 2.7.6, Django 1.6.7

from cookiecutter-django.

The machine I was using is Ubuntu 13.10, Python 3.3 and the Django specified in your cookiecutter (1.7).

from cookiecutter-django.

Thanks this helped me to solve django.db.utils.OperationalError: fe_sendauth: no password supplied issue

from cookiecutter-django.

for newbies like me just uninstall whatever database you are using and install it again, and also check if you mispelled the 'PASSWORD' i cracked my head and found that i only have one 'S' :D

from cookiecutter-django.