Re: Automated updating of data across staging and production environments?

Do you need to preload the staging database with production data in order to properly test the site? If not, you could create a fresh staging database (no data) every time you update staging. After people test it and if there are no issues, you could use dumpdata with natural keys to export the staging data. Then convert the primary keys to null. Finally, use loaddata to load the data into the production database. Using Fabric, as Victor mentioned, would be a step towards automating the process.

Kevin

On Thursday, July 26, 2012 10:29:58 AM UTC-4, Victor Rocha wrote:

I partly agree with the above question. It's a solution, but you usually never want to use your production database on a development server. 

As for his problem, I would look into fabric. You can easily write a function that dumps data from one database and into another.

On Thursday, July 26, 2012 6:10:33 AM UTC-4, Lloyd Dube wrote:

Hi all,

We have an Ubuntu Linux server which is running virtual environments (one for staging, one for prod.). Our clients test their sites on the staging environment and then proceed to capture the same data on the live sites. They want to be able to, at the click of a button, migrate only the latest data to the live sites. If users have submitted new data (e.g. contact requests) on the prod. server, this data must not be affected.

Is it possible to achieve this, and if so, are there any tools oout there to consider? Any feedback would be appreciated.

Thanks.

--
Regards,
Sithembewena Lloyd Dube

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/-5TLxRPI8J4J.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.