• Recreate the webapps for backend
• Validate the backend services
• Temporarily point the stage server to the backend
• Validate the stage server
• Configure the Arda.Main in production

Our current VSTS isn't scriptable

• Enumerate all the services using Redis (it should be only Permissions)
• Configure the services with the secondary Key
• Reset the primary Redis Key
• Restart and validate all the services

• Create a new user with db_onwer (not db_manager)
• Configure the services with the new connection string
• Validate all the services
• Reset the sysadmin password

• Evaluate all the services using storage account (should be only kanban)
• Reset the primary key (there is very little usage against storage account)
• Configure the service to use the new primary key
• Validate the services

Use docker-compose.

Use this document as a guide:
https://github.com/docker/labs/blob/master/windows/windows-containers/MultiContainerApp.md

Create a specific container for the demo. In this container, we could include all settings related to a demo environment. We will use dedicated resources for Redis and SQL, but rely on a shared AD at this time.

AD Authentication is hard because

• It has to be provisioned and set up
• It requires a fixed ReturnUrl

The deployment spends most of the time during pulling the docker images.

Right now the build process create the ardafull image.
We still need to:

• Push the image to Docker Hub
• Update the ArdaFull-Demo image (and push to Docker Hub)

The process has more manual steps when it involves updating ardabase image. In that case, it is all manual.