Day 23: The Deployment
273
# config/rsync_exclude.txt .svn /web/uploads/* /cache/* /log/* /web/*_dev.php /web/frontend_cache.php You can also create a config/rsync_include.txt file to force some files or directories to be transfered.
Even if the project:deploy task is very flexible, you might want to customize it even further. As deploying can be very different based on your server configuration and topology, don’t hesitate to extend the default task. Each time you deploy a website to production, don’t forget to at least clear the configuration cache on the production server: $ php symfony cc --type=config
Listing 23-25
If you have changed some routes, you will also need to clear the routing cache: $ php symfony cc --type=routing
Listing 23-26
Clearing the cache selectively allows to keep some parts of the cache, such as the template cache.
See you Tomorrow The deployment of a project is the very last step of the symfony development life-cycle. It does not mean that you are done. This is quite the contrary. A website is something that has a life by itself. You will probably have to fix bugs and you will also want to add new features over time. But thanks to the symfony structure and the tools at your disposal, upgrading your website is simple, fast, and safe. Tomorrow is the last day of the Jobeet tutorial. It will be time to take a step back and have a look at what you learned during the twenty-three days of Jobeet.
-----------------
Brought to you by