Azure application deployment preparation. FTP

Creating App Service is quite easy thoue it takes some time. Afterwords I have fully functional web site. Well not exactly it's web site server without any application. Now I need to deploy my applications to Azure. There are few ways to do it, but first it would be nice to set the deployment credentials with are used by FTP or Git for authentication.
Deployment credentials are set on client level, that means - it doesn't matter on with App Service I will set or change deployment credentials they will be changed for all services.
When credentials are set on App Service Overview you can find FTP user name as well as FTP address. Deployment credentials are set on client level and user for FTP is in fact one. And the FTP address is one per user. That's why App Service name is always added as first part of actual web app ftp user - just to recognize where the FTP should connect (the default directory).



I have ftp access, and two empty web applications. Lets see what's inside. Yeah the emptiness is not so empty. On my presentation below I copy ftp address and credentials to FileZilla from app service overview. First you can see the .Net application. It's simple structure with wwwroot and deployments as most important folders.
Then I'm looking at java web application. What happened here to create such complicated structure? Azure creates basically the same structure as in .Net, but additionally there is also Apache ready to use. 
Second addition is Repository - it's git repository that is already set on web app (External Repository Project that you can see on overview of my SimpleTomcat web app). 
You can connect to this repository from your favorite tool as soon as application is created.

And here you can see the structure browsing in one gif.

Now that we have ftp and git configured we can finally make some deployment.

Comments

Post a Comment

Popular posts from this blog

Azure post deployment scripts

Image
Let's do a trick. After deploying application (that was easy with Ftp or Git ) it would be nice to take some action. For example send an email, or write release notes to release page. I will do much fancier thing - I will write some text to console output.
Read more

Mobile view lifecycle. Fixing Xamarin.Forms Page lifecycle

Image
For mobile applications the highest priority is user. What user can see and interacts with. Application should react not only on user interacting with it but also user interacting with operating system. That's why not only application has it's own lifecycle but also "view" has it's own lifecycle. In Android view is represented by activity, or a fragment (the right side of android diagram). In iOS view has it's own set of lifecycle methods. In both cases view has the information that application(in this case view itself)  is being suspended and reactivated. View know quite a lot about outside world and view lifecycle is very similar to application lifecycle. Compare below first application and then view lifecycle diagrams: In Android view is represented by activity, or a fragment (the right side of android diagram). In iOS view has it's own set of lifecycle methods. In both cases view has the information that application(in this case view itself)  is
Read more

Mobile application life-cycle Android vs iOS vs Xamarin.Forms

Image
Lifecycle. One of the most common recruitment questions. No matter what technology you work with this is something that should be well known and understood. It's good to know how application behaves, what it is allowed depending on its state and when to react on specific lifecycle events. In mobile world lifecycle is even more complicated because there is no 1 answer but 3 in this case: Android. iOS. Xamarin.Forms. I use also Xamarin.iOS event names in my diagrams, but the sequence is the same. Lifecycle is the definition when your application have access to resources and when react on state change. For mobile the biggest priority is what user can see and interacts with, so active application have priority in using system resources. System has limited pool of resources, so  applications running in background (not visible to user) is limited by system in how much resources can it use and also system decides when application needs to release all resources (be closed/killed/end o
Read more