2
I have a Web App on Azure and created an internal folder as a virtual directory for a third-party developer to deploy a contracted system. I’m having great difficulty creating an FTP that only has access to the /commercial directory within the hosting. Does anyone know how to create these credentials ?
3
Azure does not implement the FTP protocol on its websites. It is another tool. It is called Webmatrix.
EDIT
I think this answer is different. Now there is a way to publish via FTP as well, but do not recommend for ASP.NET MVC because much of the automatic settings are made by Web Deploy.
2
Finally, Azure does not allow you to create a user for a subfolder. It was necessary to create a resource in my application where the person could upload the project in . zip and the process unzipped inside the folder. Problem solved.
2
Daniel,
The Azure Webapp service does support publishing via FTP, but it gives you access to the entire publishing area and has no support for specifying access to a specific folder.
What is recommended to do in this your scenario is to create two Webapp services:
And then you organize your addresses with subdomains.
Now, to meet something like dominioprincipal.com.br/solucaoterceirizada, only if the third party sends you the sources, you can do the merge of the two applications and rise in a single hosting.
But because it’s outsourced, I prefer the first scenario, so the outsourced solution - which, theoretically, you don’t have control over the way it was developed - will run under a host independent of the main one. So, if she has a problem and falls, she will not drop along with the main app. And vice versa.
I agree with your solution including practice it in other cases, but specifically this needed to be published in /outsourced solution. The solution was to create a process in my application where it can upload directly into the folder, even with the risks.
Browser other questions tagged c# asp.net-mvc windows-azure
You are not signed in. Login or sign up in order to post.
Gypsy, Azure Webapp implement SIM FTP on their websites. Posts can be made via FTP, Webdeploy or Continuous Deployment from VSTS, Github, Dropbox, Onedrive, etc. Here’s an example of Publication in Azure via FTP
– Thiago Lunardi
@Thiagolunardi Thanks for the link. I updated the reply.
– Leonel Sanches da Silva
Cool, Gypsy, I took the downvote. However, the automatic settings also work when deploying via FTP. Visual Studio first builds the release build, applies all the *.config pre-build and transformation settings, creates a publishable package, and climbs up that package via FTP. The process is really WORSE - I don’t like it -, but the final product that is delivered is exactly the same as Webdeploy.
– Thiago Lunardi
@Thiagolunardi Almost. The automatic migration header of the Entity Framework is placed by the Publish interface. You can put manual too. I didn’t want to go too deep on this answer because it comes out of the question’s purpose. I just commented because of the tag, which is like ASP.NET MVC.
– Leonel Sanches da Silva