This repository has been archived by the owner on Sep 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 652
Deployment Logic Flow
davidebbo edited this page Oct 24, 2012
·
3 revisions
Updating the repository with the new changes, at this point the folder: site\repository
will have the pre-compiled website with all the new changes.
Options:
- .NET Web Application (has a .csproj or .vbproj file).
- .NET Web Site (has a solution and no proj files).
- Other, treated as the basic deployment path.
Custom deployment is not part of this doc yet exists since it's the part we are about to change.
- Prepare temporary path.
- Build project to temporary path.
- Smart copy from temp path to web root (also: use previous manifest for the smart copy and create a new manifest after the copy completes).
- Delete temporary path.
- Build web site to current repository path.
- Smart copy from repository path to web root.
- Smart copy from repository path to web root.
- Download npm packages on web root (using npm install).
- Add IIS node configuration (if required == no web.config and this looks like a node.js web site).
- Select node version (if required == looks like a node.js web site).
Update the deployment status (the deployment is finished and active).