Deploying FloodzillaWeb - Revision history

DaveSanderman: /* Deploying FloodzillaWeb */

2020-09-08T17:16:32Z

Deploying FloodzillaWeb

DaveSanderman at 17:14, 8 September 2020

2020-09-08T17:14:50Z

DaveSanderman: Created page with "== Deploying FloodzillaWeb == FloodzillaWeb is hosted on Microsoft Azure. This is a step-by-step guide for how to deploy the website code using Visual Studio 2019. Note tha..."

2020-09-08T17:09:21Z

Created page with "== Deploying FloodzillaWeb == FloodzillaWeb is hosted on Microsoft Azure. This is a step-by-step guide for how to deploy the website code using Visual Studio 2019. Note tha..."

New page

== Deploying FloodzillaWeb ==

FloodzillaWeb is hosted on Microsoft Azure. This is a step-by-step guide for how to deploy the website code using Visual Studio 2019. Note that the details of the dialog boxes have changed multiple times and will likely change again; any text and screenshots in this document may be out of date...

This document describes publishing to both the production system ("floodzillaprod") and the beta/testing site ("fzbeta").

This document also assumes that you have access to the Microsoft Azure Sponsorship subscription that SVPA uses for hosting, and that you have sufficient rights to publish new code.

=== Initial deployment ===

The first time you deploy to Azure, you have to go through a number of steps to set up the deployment. This also applies in a new branch or a new git enlistment.

To create the deployment settings:
# In Visual Studio's Solution Explorer, right-click the FloodzillaWeb project and select "Publish...".
# Select "Azure" as the publishing target ("Where are you publishing today?"
# For Specific Target, choose "Azure App Service (Windows)"
# Select the appropriate App Service: "floodzillaprod" for production or "fzbeta" for beta.

At this point, you should see a Publish Settings page that looks something like this:

[[File:publishsettings.png]]

{{X!}} This next block may change. See the talk page for an explanation.

Hit "Edit" to customize the deployment. Under "Settings"/"File Publish Options", check "Remove additional files at destination".

You are now read to deploy. Hit "Publish". If all goes well, in a few minutes a browser window will pop up pointing at your freshly-deployed site.

← Older revision		Revision as of 17:16, 8 September 2020
Line 35:		Line 35:

	You are now read to deploy. Hit "Publish". If all goes well, in a few minutes a browser window will pop up pointing at your freshly-deployed site.		You are now read to deploy. Hit "Publish". If all goes well, in a few minutes a browser window will pop up pointing at your freshly-deployed site.
		+
		+	=== Troubleshooting ===
		+
		+	Occasionally I've seen an error on the newly-deployed site: "ANCM Failed to Find Native Dependencies". Redeploying the site appears to solve the issue.

← Older revision		Revision as of 17:14, 8 September 2020
Line 6:		Line 6:

	This document also assumes that you have access to the Microsoft Azure Sponsorship subscription that SVPA uses for hosting, and that you have sufficient rights to publish new code.		This document also assumes that you have access to the Microsoft Azure Sponsorship subscription that SVPA uses for hosting, and that you have sufficient rights to publish new code.
		+
		+	=== Prerequisites ===
		+
		+	Before deploying the website, the React.JS client code must be built and copied into place. From the react-fz-client directory, run the following:
		+
		+	* npm run build
		+	* copybuild.bat
		+
		+	This should create a new build of the client and copy it into FloodzillaWeb\wwwroot.

	=== Initial deployment ===		=== Initial deployment ===