A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Per Nergård (MVP)
Sep 28, 2012
  3289
(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.

Please login to comment.
Latest blogs
ScheduledJob for getting overview of site content usage

In one of my current project which we are going to upgrade from Optimizely 11 I needed to get an overview of the content and which content types we...

Per Nergård (MVP) | Jan 27, 2026

A day in the life of an Optimizely OMVP: Migrating an Optimizely CMS Extension from CMS 12 to CMS 13: A Developer's Guide

With Optimizely CMS 13 now available in preview, extension developers need to understand what changes are required to make their packages compatibl...

Graham Carr | Jan 26, 2026

An “empty” Optimizely CMS 13 (preview) site on .NET 10

Optimizely CMS 13 is currently available as a preview. If you want a clean sandbox on .NET 10, the fastest path today is to scaffold a CMS 12 “empt...

Pär Wissmark | Jan 26, 2026 |

Building AI-Powered Tools with Optimizely Opal - A Step-by-Step Guide

Learn how to build and integrate custom tools with Optimizely Opal using the Opal Tools SDK. This tutorial walks through creating tools, handling...

Michał Mitas | Jan 26, 2026 |