Per Nergård (MVP)
OMVPSaaS CMS Developer CertificationCommerce Connect 13 Developer Certification +2
Sep 28, 2012
visibility 3630
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
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026