Databases grow even when not a lot of new content is created. What happens is drupal mysql tables start to create overhead, especialy on tables with a lot of deletions. Cache tables, watchdog, access log, variable, ... . Sites that have been running for almost 5 years like this site for example create lots of overhead.
Optimize mysql tables
The goal of automating deployment is to make introducing new features easier. In this post we will learn how to set up a workflow that will move code and configuration of your drupal site from your local development station, to development, to staging and to production all by a using your version control and a push of a button.
Branching and merging with git is one the features that make it worth to use git. Having a successful branching model is key to be able to respond to everyday needs.
Why create the overhead? The simple use case when a project is in production and new features are being developed requires that you have a work flow that allows introducing fixes without having to release the entire development code. You dont want to wait for a stable release of all features currently in development.
This post will give you a list what to check when you go live with a drupal 7 website and how you can control it and automate it. You need to check this go live checklist each time you keep integrating new stuff during deployment to test if everything is still working. To save time this task can be automated.
