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 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 safer than a single DB user with access to all site > databases. > > In any case, I think you should be able to import the database as the DB > user "project_name", it's the owner of all tables as seen here: > > https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/fabfile.py#L494-L501 > > > Also, not sure if it helps but you can backup and restore your database > directly from fabric too. > > fab backup:"mybackup.psql" > fab restore:"mybackup.psql" > > > https://github.com/stephenmcd/mezzanine/blob/master/mezzanine/project_template/fabfile.py#L347-L367 > > > Hope that helps. > -- 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.
