0

At my work we have a .NET web application that is hosted in Azure. We use TeamCity to build our application and Octopus to deploy the application to Azure. We've been noticing that our deployments have started to increase in duration so I've been looking at the Octopus logs and it appears that the duration is mainly due to the multitude of front-end files we are using. We have recently implemented React so we have the node_modules folder plus all the other .css and .js plugin files that our front-end uses.

Are there any strategies to deal with said files and reduce the burden on deployments? Open to crazy ideas like zipping or using Docker containers - anything to make the deployments scale better as our application gets larger.

dhughes
  • 645
  • 1
  • 7
  • 19
  • 1
    when did zipping become crazy? – benPearce Jun 29 '17 at 05:29
  • What does your deployment process actually look like? I would have assumed that this is a pretty vanilla "Deploy NuGet" step, followed by web site configuration to point at the extracted folder. It's early... I'm probably missing something. – gvee Jun 29 '17 at 07:10

1 Answers1

0

Why not go with the hype and use webpack? As opposed to other hypes.. this is practical and actually useful.

webpack-mechanics

Image source: http://www.pro-react.com/materials/appendixA/

evilSnobu
  • 24,582
  • 8
  • 41
  • 71
  • We use webpack to bundle our own React files. Are you suggesting we use webpack for **all** javascript and css files, ours and third party? – dhughes Jun 23 '17 at 13:06
  • Yes, you could also bundle 3rd party stuff separately - here's a broader thread on that -- https://stackoverflow.com/questions/30329337/how-to-bundle-vendor-scripts-separately-and-require-them-as-needed-with-webpack – evilSnobu Jun 23 '17 at 13:39
  • Alternatively you could .zip everything up and call Kudu's ZIP API if you're hosted on App Service -- https://github.com/projectkudu/kudu/wiki/REST-API#zip – evilSnobu Jun 23 '17 at 13:43