Re: [mezzanine-users] Why does Fabric deployment name the db user after the project?

2016-07-12 Thread Geoffrey Eisenbarth
Hey Eduardo, thanks for all your help with the Fabric implementation, it's been very appreciated! I'll check out your suggestions today, I think using fab restore to import my database is the way I should be going. On Monday, July 11, 2016 at 8:12:18 PM UTC-5, Eduardo Rivas wrote: > > I think

Re: [mezzanine-users] Why does Fabric deployment name the db user after the project?

2016-07-11 Thread Eduardo Rivas
I think the idea is to be consistent and predictable when it comes to naming all things. The project directory, the database user, the database itself, and all configuration files just use the project name as identifier. I'm no security expert but I think that having one DB user per site is

[mezzanine-users] Why does Fabric deployment name the db user after the project?

2016-07-11 Thread Geoffrey Eisenbarth
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