Subscribe to Newsletter
#

Best practice in deploying Nopcommerce from Development to Test to Production environment

Following the best practices when it comes to deployment in your development workflow is critical. This is because a bad production deployment can ruin all the efforts that you have invested in a development process. Finding and maintaining a solid development flow can be the biggest asset for a company. We are explaining below for the benefit of our readers the best practice in deploying nopcommerce from development to test to production environment.

Steps to be followed while deploying a nopcommerce website from Dev to Test to production environment:

Best practice in deploying Nopcommerce from development to test to production environment usually involves at least three environment based steps:

  • Initially the developers work on bugs and features and are mostly committed directly to the stable development branch. When these features are implemented, these are then deployed to the quality assurance and testing environment.
  • After testing is complete, feature branches are merged into the development branch.
  • On the release date, the development branch is merged into production and then deployed to the Production environment.

Checklist to be followed for the Environmental Details in the Hosting Server

  1. Server Type(VPS or Dedicated)
  2. Operating Systems (32bit/64bit)
  3. IIS Details (6.0/7.0)
  4. MSSQL Database versions (2005/2008/2008R2)
  5. Dot Net Framework version(2.0/4.0)
  6. Hardware specifications (RAM/HDD/CPU)
  7. Firewall Status (In-built/External)
  8. Modules Integration (In-built/Third Party)
  9. Nop version (2.4/2.5/2.6)
  10. Hosting Panel (Website Panel/Plesk)
  11. MVC 3 Installed Yes or No

Best practice in deploying Nopcommerce from Development to Test to Production environment

  • You must make sure that there is a matching up between these three environments – Development, Testing and Production.
  • Always back up the code and db from source server to upload the destination server directly. Sometimes we need to download the code at our end if site is not able to configure directly to the destination server.
  • After the deployment is done, you must ask the QA team to compare the demo site with the live site. Only after this should th domain be pointed to the destination server.

We recently deployed a nopcommerce website from the development to testing stage and then to production environment. This client deals in centralizing the marketplace for templates, add-ons and applications online. Our team is expert at handling such type of deployments and was able to configure the website in the live production environment in no time. They always follow the best migration steps for accuracy and to avoid the downtime. Here is an example of us following best practice in deploying Nopcommerce fom development to test to production environment.

NopCommerce Deployment

Figure 1

Please feel free to request assistance if you need information on best practice in deploying Nopcommerce from development to test to production environment.