Per Nergård (MVP)
+1
Sep 28, 2012
visibility 3499
star star star star star
(6 votes)

Deployment center wish list

I’ve been using deployment center quite a lot lately and since it hasn’t been all fun I have a couple of features I would like to see to make life easier in the future.

1. Add installation option

Add a choice for if DPC should be available for all users or just 
the user installing it.

2. Split the upgrade site with database option into smaller parts

Instead of having a big bang upgrade option I would like to see another option where the upgrade are split into three parts: database, DLL and other files and lastly configuration file changes.

In the current version of DPC if something goes wrong with the SQL connection the entire installation fails. This leading to either manually running the SQL scripts or setting up a temporary site somewhere to do the upgrade. And the same goes for the configuration files.

If the options are split up the “worst” we have to do is install DPC on the SQL Server for the DB upgrade and the rest can be done on the webservers.

I don’t know the inner workings of DPC so my wishes may be hard to implement but since I haven’t read any thoughts about DPC I had to share my $0.2

Sep 28, 2012

Comments

Sep 28, 2012 03:00 PM

Great! Have been requesting this in the forums.

Arild Henrichsen
Arild Henrichsen Sep 28, 2012 04:03 PM

+1 on this Per. Especially #2 has given me some grey hairs at times. Make it happen!

Frederik Vig
Frederik Vig Sep 29, 2012 04:00 PM

#2 is an important one that will save a lot of time

Sep 30, 2012 05:25 PM

I second. Having an option just to upgrade the database is vital for deploying if you have config and files under source control.

Oct 1, 2012 01:02 PM

+1 Fredrik

Oct 1, 2012 04:32 PM

+1 Fredrik

Mari Jørgensen
Mari Jørgensen Oct 1, 2012 07:26 PM

+1 for option #2

Thomas Solbjør
Thomas Solbjør Oct 1, 2012 08:55 PM

+1 for option #2

Oct 2, 2012 08:15 AM

+1 for option #2 - Great initiative Per!

per
per Oct 3, 2012 03:06 PM

Good suggestions on upgrading. Point 1) is a bug really, we did not notice that Deployment Center was not available to all users so that has been changed in 7.

error Please login to comment.
Latest blogs
Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |