Well, actually I understand initial deployment, but: like many others, I typically have at least two versions of a particular website: the live one (on shared hosting) and a local development version.
The remote database of the live site will continuously change and expand: visitors will post forum threads, and content editors will add articles.
The local database of the development site will also change: the content is not important here, but there will be changes to Sitefinity tables, e.g. when I change widget templates.
Suppose it's time to upgrade the live site to the new "release" I have build and tested locally. What do I do? I can't just script my local database and run that on the remote database. I will loose all content. As far As I understand it, just certain (parts of?) the local tables should be scripted and deployed on the remote database. What is the recommended way to manage this process?
I'm evaluating Sitefinity and don't understand yet how to do this.