We've noticed a lot of situations where project:deploy gets us into trouble:
* The permissions are acceptable locally (because MAMP runs as the same user as the developer) but not remotely * Migrations don't get run automatically on the far end * symfony cc doesn't get run automatically on the far end The new pkToolkit:deploy task is a safer wrapper for project:deploy. It does the following locally: project:permissions project:deploy --go servernickname Then, on the remote server (via the ssh credentials in properties.ini), it does: ./symfony cc ./symfony doctrine:migrate --env=environmentname This takes care of most of the common ways a site is left in a nonfunctional state after the deploy task is run. You call it like this: ./symfony pkToolkit:deploy servernickname remoteenvironmentname Example: ./symfony pkToolkit:deploy production prod pkToolkitPlugin is part of the Apostrophe CMS plugin suite (www.apostrophenow.com) and can also be used on its own. Give it a look: http://www.symfony-project.org/plugins/pkToolkitPlugin Hope this is helpful! -- Tom Boutell P'unk Avenue 215 755 1330 punkave.com window.punkave.com -- You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-us...@googlegroups.com. To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en.
