WAWSDeploy | Simple command line tool to deploy a folder to an Azure | Azure library

by davidebbo C# Version: Current License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | WAWSDeploy Summary

WAWSDeploy is a C# library typically used in Cloud, Azure applications. WAWSDeploy has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Simple command line tool to deploy a folder or a zip file to an Azure Website using WebDeploy. See this [post] for details. Note: the .PublishSettings file discussed here is the one you can download for a specific Azure Web App via the portal. With optional password argument. Delete files on the remote host. Use checksums instead of timestamps. Target Path - The virtual directory to deploy to. Target Path - Using a physical target folder. App offline - Attempt to turn ASP.Net application off before deployment. Setup a higher number of retries in case of deployment failure (WebDeployment default is 5). Setup the interval (in milliseconds) between each deployment attempts in case of deployment failure (WebDeployment default is 1000ms). Skip the app_data directory during the deployment. User defined folders regular expressions that should be skipped during deployment.

Support

Quality

Security

License

Reuse

Support

WAWSDeploy has a low active ecosystem.

It has 45 star(s) with 35 fork(s). There are 8 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 9 have been closed. On average issues are closed in 121 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of WAWSDeploy is current.

Quality

WAWSDeploy has 0 bugs and 0 code smells.

Security

WAWSDeploy has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

WAWSDeploy code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

WAWSDeploy is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

WAWSDeploy releases are not available. You will need to build from source code and install.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of WAWSDeploy

Get all kandi verified functions for this library.

WAWSDeploy Key Features

No Key Features are available at this moment for WAWSDeploy.

WAWSDeploy Examples and Code Snippets

No Code Snippets are available at this moment for WAWSDeploy.

Community Discussions

Trending Discussions on WAWSDeploy

Azure function returns error: No job functions found. Try making your job classes and methods public

Error loading hostpolicy.dll while deploying .NET Core console app to Azure WebJobs

Docker image is completely borked and won't start

QUESTION

Azure function returns error: No job functions found. Try making your job classes and methods public

Asked 2019-Sep-06 at 08:59

I have created an Azure Function application in Visual Studio 2017 and can publish it to Azure without any issues using the Visual Studio publish functionality (right click project then select Publish).

As deploying from a developers instance of Visual Studio isn't an ideal continuous integration strategy, I have created a deployment pipeline with TeamCity and Octopus where TeamCity builds the Azure function application and Octopus uses the WAWSDeploy application to deploy the Azure Function files to Azure. The deployment works fine and I when I view the Azure function files when deployed via WAWSDeploy, the files are exactly the same as when I publish the Azure Function application from Visual Studio.

However I get the errors No job functions found. Try making your job classes and methods public. and Invalid script file name configuration. The 'scriptFile' property is set to a file that does not exist. when I deploy (by viewing the Azure Function application logs) from WAWSDeploy. This doesn't appear to be a WAWSDeploy issue but it looks like the Visual Studio publish function is doing something I'm missing. Any ideas?

Folder structure of Azure function files:

...

ANSWER

Answered 2017-Jun-21 at 04:25

Issue was caused by having an incorrect scriptFile value in the function.json file. When I published the Azure function from Visual Studio, this value is set correctly but when I build the Azure function and push the files to the Azure function application manually, the scriptFile value is missing the bin folder in the path to my function dll file. During my build process, I now hack the scriptFile value to set it correctly.

Source https://stackoverflow.com/questions/44643347

QUESTION

Error loading hostpolicy.dll while deploying .NET Core console app to Azure WebJobs

Asked 2019-May-28 at 11:02

I have followed this tutorial to deploy a .NET Core console application to an Azure Web Service WebJob.

My app is running locally without any issue (with dotnet 1.0.0-preview2-003131) but when I try to run it from Azure console I have the following error :

Failed to load the dll from [D:\local\VirtualDirectory0\site\wwwroot\app_data\jobs\triggered\PopcornExportWebJob\hostpolicy.dll], HRESULT: 0x800700C1

An error occurred while loading required library hostpolicy.dll from [D:\local\VirtualDirectory0\site\wwwroot\app_data\jobs\triggered\PopcornExportWebJob]

The version of Azure dotnet is 1.0.0-rc4-004771 and the hostpolicy.dll file is the same than I use locally. In fact, when I download the zip of my deploy from Azure and when I run it locally, it is working fine. But it fails on Azure environment.

Also, here is my project.json:

...

ANSWER

Answered 2017-Feb-22 at 21:05

Alright, I've figured it out.

If you want to deploy a dotnet core app to Azure Web Service, include the runtime "win7-x86" if you are running your app in 32-Bit platform mode.

For a Visual Studio 2015 solution, your project.json should include :

Source https://stackoverflow.com/questions/42396782

QUESTION

Docker image is completely borked and won't start

Asked 2018-Sep-13 at 17:29

I'm running Docker for Windows and trying to build an image. It was working great, but then I added this to the end of my Dockerfile:

...

ANSWER

Answered 2018-Sep-13 at 17:29

So, I seemed to have solved it. At least in my case since, as mentioned in the comments, this error is rather generic and doesn't mean one thing in particular.

First, I had to completely comment out everything from my Dockerfile after installing Chocolately on down. This built and also ran. Next, I uncommented one thing at a time. Each time, I'd build and run. Eventually, I'd run into the error (either building or running) and I'd shift some things around and maybe it would work another time. No matter what I tried, I could never get everything to run.

The overall issue, it seems, is that you just can't do that many things in a single Docker build. I believe I was hitting some sort of limit with the number of layers that could be built.

The Solution:

It turns out Chocolately is able to install multiple packages at once. So, I replaced all my RUN commands with a single one:

Source https://stackoverflow.com/questions/52316924

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install WAWSDeploy

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: