Azure deploy. Local Git Repository

Besides FTP there are other ways to deploy application to App Service. You can read more here.
It was not so clear for me from the official explanation. I really thought that it's about the local repository based somewhere in my company's basement. But it turns out that this is repository local to Azure. It's fully functional git repository. You can see the history of my commits as example.



Setting the git repository. Well this is not about storing code (not primarily) it's supposed to be the deployments related so it is set on Deployment Options tab. I choose Local Git Repository and then on Overview I can get my newly set git URL. The credentials are the same as for FTP connection.
From now on I can use git-favorite-tool to browse, insert, update file on my Azure web site, just like using FTP, well not exactly because Git main directory is wwwroot directory (see the structure on Ftp in this post).

Every time I update git repository with new WAR file Azure runs the deployment and updates application for me.
This is very simple deployment method, but it's not so great for production because for example there is no way to set Continuous Integration. But it still provides some level of package and deploymnets control whit git history.




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