Azure App Service console

App Service Plan under the hood is a virtual machine with some pre-installed application like IIS. It's a little more complicated than just a VM per App Service Plan, and I as a user cannot access or change this machine. Well this is possible but in a App Service Environment.
If you go down in list of App Service available tabs you'll find Console.
This is fascinating tool. It is just a console.. but it's on App Service Plan virtual machine.

Let's say I'm curious and from starting point of site I want to know what is on drive.
I can do it without any problem. This is just CLI so cd.. dir combination gives me main drive content.
Ooh there is a Program Files directory... with lots of stuff: IIS (obvious), Go, MySql, MSSQL, PHP, PowerShell, IISNode, PortBridge (Azure ServiceBus connectivity). Even more in Program Files (x86) like Java, apache, bower, grunt, Git, Mercurial, Python.

This is the proof that you can use App Services with different languages and technologies not only .NET Framework and C# (well it's always easier in C# ;))


Of course this console can be used to something more productive - like accessing deploymnet log files, or just checking if file are on their place.

I have one more interesting and worth remembering link. Azure Virtual Machine Internals description.

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