Yes project:deploy is entirely wrong for content unless you are moving code and data in the same direction. We do that only rarely - first deployment of a staging server, first deployment of a production server. And it doesn't copy databases at all. The sync-content plugin understands about databases and uses Symfony's standard sfDatabaseManager class to get the MySQL credentials. Special helper tasks are run remotely to dump and load SQL back and forth over the ssh connection. But you don't have to think about this; it just works. (:
On Sep 29, 6:18 pm, Eno <[email protected]> wrote: > On Tue, 29 Sep 2009, Mariusz Sasinski wrote: > > And why not just use symfony project:deploy ? > > deploy:project is too simpplistic for some cases. We have separate > clusters for different types of servers and they need different kinds of > content synced. > > -- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
