2014-03-06 18:36 GMT+01:00 Federico Bruni <fedel...@gmail.com>: > 2014-03-06 18:20 GMT+01:00 Federico Bruni <fedel...@gmail.com>: > > 2014-03-03 13:01 GMT+01:00 Federico Bruni <fedel...@gmail.com>: >> >> First of all, the DATABASES options are divided in 3 files: >>> >>> - local_settings.py: the setting for local development. By default, >>> sqlite is used. I wonder what's the best approach if I know that I want to >>> deploy on PostgreSQL on the server. Should I work on PostgreSQL locally as >>> well? >>> - live_settings.py: this also is pretty clear, it contains the server >>> settings (I found out that it can be left untouched, as long as settings. >>> py is complete) >>> - settings.py: IIUC, any settings here will be overridden by the two >>> settings above, so I can ignore the DATABASE section. Is it correct? >>> >> >> Can anyone please reply on the last question above? >> >> I've managed to sync local and server manually, but I'd like to be able >> to do it with Fabric. >> One problem may be that the owner of the database created by Fabric is >> always %(proj_name)s, no matter what I put in the settings. I've tried to >> write the server user name (string) both in settings and live_settings.py, >> but fabric seems to ignore it. >> >> > The awful "workaround" is deleting the database created by fabric and then > doing a manual dump. > My site is live now, but I'd really like to know what's wrong with my > configuration. > > Or rather, why I don't keep a message in the drafts and send it just the day after? :-) I've already been told that Fabric doesn't sync the content of the database. So the manual operation _is_ required.
Sorry for the noise, I've had few time to spend on Mezzanine lately -- 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 mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
