Objective

Become familiar with how the SOAJS Dashboard notifies you about catalog recipe updates for the Nginx that is deployed in Dashboard Environment and learn how to pull and apply these updates in the Dashboard Environment.

Steps

1. Understand what Catalog Recipe Updates mean and Locate the Update Notifications
2. Apply the Code Update

Step 1

The Dashboard contains a notification system that informs you whenever new catalog recipe updates or upgrades.

Catalog Recipe updates happen after you deploy an nginx. Upon deploying a SOAJS cloud, the installer creates recipes for Nginx and the SOAJS services that were deployed in the Dashboard Environment.

These recipes can be modified under Develop → Catalog Recipes in the Dashboard. Whenever you change any of the recipes used by the installer to deploy the nginx in the dashboard environment, the dashboard notifies you so can apply these changes on the nginx.

These notifications appear Under Deploy pillar → Updates & Upgrades.

In Updates & Upgrades you will see notifications about new catalog recipes and which services were affected.

Step 2

Once a catalog recipe has been updated, you can apply it on the deployed services as follow:

1. Go to Deploy pillar → Clouds & Deployments
2. Click on the Nginx Tab
3. Lookup the nginx entry
4. 1. Open the Service Operations menu
   2. Click Redeploy Service

Redeploy Service

This operation will load the catalog recipe again, if the catalog recipe has changed then the nginx will be affected then it redeploys the nginx with the new recipe changes.

The SOAJS deployer inside the SOAJS image will run and clone the SOAJS Dashboard default UI again, if there are changes then they will be pulled then it will check if you have any Custom UI modules if you have provided them in the recipe and pulls them as well.

Then it will build the upstream configuration to point to the SOAJS Controller and create the virtual host entry for the Dashboard UI widget and start the nginx server.

While the deployer is running, your old nginx remains operational until the new one is flagged as running by either Docker Swarm or Kubernetes depending on which of the two drivers you have chosen.

When the new nginx becomes ready, then the old one will be terminated; your Nginx is now updated and is using the latest catalog recipe.