1.0.0releasedDatabase Synchroniser
Log database changes to easily synchronise structure (sections, fields, pages) development and production databases, without affecting content.
Clone URLhttps://github.com/symphonists/db_sync.git
Add as a submodulegit submodule add https://github.com/symphonists/db_sync.git extensions/db_sync --recursive
Compatibility
2.x.x | 2.1.x | 2.2.x | 2.3.x | 2.4.x | 2.5.x | 2.6.x | 2.7.0 | 2.7.1 | 2.7.2 | 2.7.3 | 2.7.4 | 2.7.5 | 2.7.6 | 2.7.7 | 2.7.8 | 2.7.9 | 2.7.10 |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
No | 0.9.1 | 0.9.1 | 1.0.0 | No | No | No | No | No | No | No | No | No | No | No | No | No | No. Soon? |
Readme
Database Synchroniser
Installation
- Download and upload the 'db_sync' folder to your Symphony 'extensions' folder.
- Enable the extension by selecting "Database Synchroniser" in the list and choose Enable from the with-selected menu, then click Apply.
Warning
As of version 0.7, queries are stored in a file named db_sync.sql
in your /manifest
folder. This file is visible to anyone, therefore I strongly advise that this extension only be enabled on development environments. Don't deploy it to production, or disable it entirely by looking for db_sync
in Symphony's config file.
Disclaimer
While this extension has worked well for my own projects, I can't guarantee its stability for your own. My workflow when using a development/staging/production environment is to install this extension on the development server only. When making a release I pull the production database back to staging where I apply the dbsync SQL file. If all goes well after testing, I back up production and run the same dbsync file there. The file is then removed locally and I can continue developing towards another release.
Please, please, please back up your production database before applying any structural changes.
Version history
Requires Symphony 2.3.x
Symphony 2.1.0 to 2.2.x