Coding best practices: Difference between revisions

Revision as of 18:36, 31 August 2023

Revision as of 19:25, 31 August 2023

Line 406:

# Adopt a multi-stage strategy: Depending on the size of the project, sometimes more deployments are needed.<ref>blog.fortrabbit.com/multi-stage-deployment-for-website-development</ref>

# Have a roll back strategy: There must be a way to roll-back to a previous (working) version.

# Rely on automation for repeatable processes: There's far too much room for human error, deployments should not be manual. Use a tool that is native to each operating system or, use a scripting language for cross-platform deployments.<ref>{{Cite magazine|url=https://www.wired.com/insights/2013/04/why-30-of-app-deployments-fail/|title=Why 30% of App Deployments fail|Firstfirst=Victor|last=Cruz|magazine=Wired|date=April 3, 2013|via=www.wired.com}}</ref><ref>{{cite web| url = http://emphaticsolutions.com/2009/09/06/the-rules-of-software-deployment.html| url-status = dead| archive-url = https://web.archive.org/web/20100513054900/http://emphaticsolutions.com/2009/09/06/the-rules-of-software-deployment.html| archive-date = 2010-05-13| title = The rules of software deployment}} </ref>

# Re-create the real deployment environment: Consider everything (routers, firewalls, web servers, web browsers, file systems, etc.)

# Do not change deployment procedures and scripts on-the-fly and, document such changes: Wait for a new iteration and record such changes appropriately.