I'm pleased to announce the first release of the sfSyncContentPlugin. This plugin adds a propel-sync-content command to Symfony, which does for content what "symfony sync production go" does for code.
A typical example of usage: symfony propel-sync-content frontend dev from staging That would pull the database, as well as folders you have configured to be treated as content, down FROM the staging server to the local instance of your project. Here's another: symfony propel-sync-content frontend dev to production That would push your content TO the production server (yes, overwriting whatever is currently there). Currently this plugin requires Propel (just barely) and MySQL (a bit more seriously, because it uses the mysql and mysqldump commands to get its work done). If you're typing a lot of mysqldump commands, or testing against crappy "test data" because you don't have a clean way to pull the production data down to your test environment, this plugin is definitely for you. Currently tested only on Symfony 1.0. Here it is: http://www.symfony-project.org/plugins/sfPropelSyncContentPlugin Enjoy! -- Tom Boutell www.punkave.com www.boutell.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
