Re: [mezzanine-users] postgres content/data syncing between development & production

On 9/06/2015 11:47 PM, Ken Bolton wrote: Hi Vikraw, Sorry if I added to the confusion. Mezzanine does not move content for you. The commands I pointed out can be interpreted and extrapolated into normal command-line commands to do database backup and restore. Moving the backups is an exercise

Re: [mezzanine-users] postgres content/data syncing between development & production

Hi Vikraw, Sorry if I added to the confusion. Mezzanine does not move content for you. The commands I pointed out can be interpreted and extrapolated into normal command-line commands to do database backup and restore. Moving the backups is an exercise left up to the reader. hth. ken On Tue, J

Re: [mezzanine-users] postgres content/data syncing between development & production

So, what i understand is that both backup and restore tasks are run on the Depoyment/remote machine. when i do - fab deploy backup is taken (last.db) before any other tasks. restore is never called for task deploy South "schema" migrations are added to the di

Re: [mezzanine-users] postgres content/data syncing between development & production

Hi Vikraw, PostgreSQL has excellent facilities for dumping and loading data. For an excellent example, read how we do it in the fabfile.py, particularly the backup and restore

[mezzanine-users] postgres content/data syncing between development & production

How can I sync the actual data in the database between development and production for postgres? new pages, products, description, Prices, Sales etc will be first checked in development. This has to be deployed to the production without overwriting/updating production relevant content ex: Past o