I'm having some issues with postgre authentication, and I'm curious as to what the reasoning was behind the database user being named after the project instead of the username given in the Fabric settings dictionary. Now I have a password-less database user that doesn't line up with the user I created for Fabric deployment, and thus can't use peer and/or md5 authentication (c.f. pg_hba.conf).
Perhaps there's something I'm not doing correctly, but this issue is coming up when I import a pg_dump .sql file, I can't use ``psql -d project_name -U project_name -f dump.sql``, and since I can't import the database as the user ``project_name``, there are issues with migration since the psql user ``project_name`` doesn't own all the tables in the database. Am I doing something fundamentally wrong here? Thanks for the input :) -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
