Update:
People have raised some good questions about my site and workload so I thought some addition information would be helpful.
My site has 1200+ plants in a garden, with multiple tables and dozens of fields. Besides basic spelling corrections other attributes may need to be changed (location, size, alive/dead to name a few). We will then be adding addition plants thought a to be developed (local access only, not on the web).
We currently manually enter changes in both database but this seems impractical as we are likely looking at hundreds of changes across the database not to mention the addition of new plants.
Background:
We are starting to look at a major update to our database which will include correcting spelling, changing some attributes, and adding new items. To me, it seems like the development database is the correct place to start these changes, and then have the migrate to the production server automatically so both have more or less the same data. I realize that the development and production databases are supposed to be kept separate, but as these changes are going to be done mostly by others I'm looking for a way to keep the development and production databases in sync in more automated fashion.
System architecture (all systems are Ubuntu if that matters):
- Data server running postgresql Development server, mostly offProduction server Workstation (I use pgadmin among other tools toaccess the various servers)
Goal:
I would prefer live syncing between the databases, but I'm ok with either hourly or daily updated if that makes it easier.
On the other hand, maybe I'm thinking about this too literally and all the changes should be made live to the production database and the development database should be updated only when the development server is turned on.
