On Tue, 29 Sep 2009, Tom Boutell wrote: > 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.
Yeah we have DEV VMs -> QA VMs -> STAGING -> PROD. We also have separate image and web servers. The image servers run lighttpd. The web servers run Apache. But we also have two types of web servers. We also have a memcache cluster :-) So only something which allows us to define and manage groups of servers has a hope of managing our environment. I have been playing with Capistrano and hope to have to all working... one day... :-) > 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. > (: Our database is a 'bit' too big to do stuff like that - the users table alone has over 12 million rows... :-) We also use an XML database too. There are slave servers for all of those and we have replication between those of course. -- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
