Precautions when deploying datapackages to the production environment

Uwaga:

Never deploy before a weekend.

Do not upgrade just before a weekend, without doing any testing beforehand, or before a vacation period.

Uwaga:

Inform the users of deployment.

  • Inform the users of the application before and after deployment.
  • Avoid deleting data from production when possible.
  • Disable operators; don't delete them.
  • Use a datapackage when deploying in Production instead of copy-pasting the parameters.
  • Avoid using the same datapackage every time you deploy changes. Create a specification with just the changes you need.
  • Back up the parameters on production before importing important parameters from development

Uwaga:

Plan to deploy on low activity periods.

Deploying changes to the data structure generates a database update. These updates can cause locks on the tables and cause issues on the operations.

Uwaga:

Check build and version numbers between two enviroments.

To avoid any side-effects, ensure that the environment where the packages have been built uses the same version and build number as the production environment.

Ta zawartość jest licencjonowana na warunkach licencji Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Posty z serwisów Twitter™ i Facebook nie są objęte licencją Creative Commons.

Informacje prawne   |   Zasady prywatności online