I don't understand deploymentCancel

The forums are in read-only mode. In case that you want to directly contact the Progress Sitefinity team use the support center. In our Google Plus group you can find more than one thousand Sitefinity developers discussing different topics. For the Stack Overflow threads don’t forget to use the “Sitefinity” tag.

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?

The way I see it, any manual changes to a system (not Sitefinity specifically) can be documented and an upgrade process can be established/automated. But since Sitefinity4 uses meta fields extensively now, most of the changes are probably done through admin back-end or through Fluent API.

The obvious way is to document all changes and go over them again in live environment, through admin setting or what other methods being used. But this seems 1, cannot be automated; 2, prone to problems (i.e. what if dev version went through several changes back and forth, lost data in the process? we definitely do not want to replicate that in live server)

You can use database schema comparison and database replication tools to merge the data. If you use two databases, Sitefinity cannot track what changes has been made in both of them. We will have plans for synchronization option in one of the 4.0 editions that will be released next year.

Greetings,
Ivan Dimitrov
the Telerik team

Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items

I know most of this thread was about general migration of changes from one environment to another, but I have the same question that Steve posed above. Do you have a recommendation for upgrading multiple environments to a new Sitefinity build? For example, our development environment is now on RC, but our test environment is still on Beta 2. If I now migrate our latest code to the test server, which includes all of the latest Sitefinity assemblies, will it automatically upgrade the test database to RC? Wasn't sure if I needed to run the project manager upgrade process on each environment...

Hi Matt,
Do you have a recommendation for upgrading multiple environments to a new Sitefinity build?

You have to use Sitefinity's 4.0 Project manager. The project manager does not support batch upgrade operations. There is no automated process for batch upgrades.

All the best,
Ivan Dimitrov
the Telerik team

Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items

The database schema comparison and database replication tools you mentioned would indeed help. However, it would still require quite some knowledge about the database structure I think. This is the way I see it:

When updating a live environment from a development environment, you would 1 and 3 to be pushed to live, not 2! In order to do so, you need to know exactly which Sitefinity tables contain 2 and which contain 3. That's actually something I do not want to think about :-)

Would this be the synchronization option that will be added later? I would be a huge help!

Ideally, I would also like to be able to push 2 (and even 1 and 3 in some cases) from live to development, in order to test and develop with actual data.

Sitefinity's database is maintained by data layer Open Access ORM. There is no simple relation between the tables and single query to get a content data involves multiple tables. For instance if you want to migrate a content like blog or/and post and you should keep its permissions and workflow status there are more than 10 tables in the query

There are many changes that are saved in config files - App_Data/Sitefinity/Configuration

All the best,
Ivan Dimitrov
the Telerik team

Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items

Tools

Sitefinity Professional Services

Progress, Telerik, Sitefinity and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries.