website-deploy | simple utility to deploy a static website | Cloud Storage library

How would I link the index.html? I am deploying in Google Cloud Platform (using gcloud app deploy). This is so I can make the website with the html. I need a example with a html provided here (any of three html is fine). The index.html is where someone navigates to the root page of your website, what the person sees when clicking or going to the link of the site. My html specifically is just a "hello world" type website. And my files are located in my project (website-deploying-gc). This is the final step to create the site. Here is where the html is located (after getting into the files):

I am ready to deploy into the Google Cloud Platform but I have ran into a problem. The website won't deploy. Here is what the code displays:

So, I am trying to deploy a personal website app and expose it to a local domain (for now) but I am always getting a 502 Bad Gateway from my nginx-ingress-controller. So, for such task I have built 3 files: deployment.yaml, service.yaml and ingress.yaml:

In my Azure DevOps release pipeline, I want to simultaneously publish a website and a database.

I'm having trouble publishing the DB, for the simple reason that on a different pipeline, for a different website, I'm already addressing that same database: same IP, and the same Port (1433).

The error message is:

Binding (172.XX.X.XX : 1433 : MyServerName) already exists for a different website, change the port and retry the operation

There is a similar thread on Stackoverflow:

Similar thread but the problem is on IIS (not SQL)

I understand perfectly that we cannot deploy 2 websites on the same IP on the same PORT on IIS, but why does Azure Devops prevent me from deploying 2 databases on the same IP on the same PORT (1433 - SQL Server standard) ? It doesn't make sense.

I am using the first pipeline task (red):

Should I use the green ones? Unlike the first, they're not Microsoft standards, they're open-source.

I would like to remember that I didn't have any trouble publishing the first website. The problem only appeared when I targeted the same database server (same IP/Port) in the second website release pipeline.

I created a site in ASP.NET Core with VisualStudio and then copied the files to the server and linked IIS (8.5) to it.

I configured a binding with localhost:443.

However, when I browse to https://localhost:443 I obtain an error:

I am trying to complete Continuous Integration/Continuous Deployment automation for a web application project. I have been helped by a series of SO posts link1, link2, link3 and things are now running, except the upload to the hosting server is longer than it needs to be; I currently upload all files instead of just the ones that changed.

When creating the TFS2017 Build (or Release) there are many Task options, including some from the marketplace. I'm referring to, in this case, the dialogue for a Build as shown below:

I'm currently using a PowerShell script which seems a little archaic and inefficient as noted above. Do any of the tasks available to us mimic the Visual Studio 2017 Web Deploy Publish Method which runs quite nicely and quickly? If not, what can I use for an 'intelligent' upload process that checks whether or not a file must be uploaded?

I'm trying to add a binding conditionally.

I would like the binding to be added if the variable exists.

Eg say there exists foo, "hello I'm foo", Production, but no such foo vairable exists for beta, then the binding would get added to Production by not beta.

I think my expression should look something like this: