Precautions when deploying datapackages to the production environment

참고:

Never deploy before a weekend.

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

참고:

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

참고:

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.

참고:

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.

이 작업에는 Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License의 라이센스가 부여되었습니다.  Twitter™ 및 Facebook 게시물은 Creative Commons 약관을 적용받지 않습니다.

법적 고지 사항   |   온라인 개인 정보 보호 정책