Does anyone know if Aptana Studio 3 can integrate directly with Azure cloud hosting like it does with Heroku or Engine Yard? Want to avoid the GitHub option if possible as public account.
From the official site for Aptana Studio 3 I see that it supports FTP as a standard publishing method.
You can use this method (ftp) to Deploy your application to Windows Azure Web Sites. And here is a quick tutorial on how to publish to Azure Web Sites using FTP. It will guide you through the process of creating deployment credentials and how to get the FTP site address.
I have been looking at other IDE solutions and recently came across PHPStorm - it has ftp, SVN and Azure integration as standard (amongst others) so am going to stick with it and because it's also an excellent code editor. Happy days!
Related
In the new Windows Azure Portal, how does the "Console" Window works? What really happens behind the scenes? I am curious to know how it works internally.
(I can't find that out for myself since I don't have an Azure account :-( )
http://assets.andrewconnell.com/media/Default/Misc/AzurePortalManager04.png
I actually made this console as my internship project while at Microsoft. It was made before the xplat-cli was available, but it's still very simple and actually uses the Kudu service. Kudu is the engine behind git/hg deployments, WebJobs, and various other features in Azure Web Sites. More information on Kudu here: https://github.com/projectkudu/kudu/
When your web application is created on azure, Kudu stands up a scm website for your web application with the end point yoursite.scm.azurewebsites.net. The console then takes commands that you give it, calls Kudu's REST API using the scm website as the endpoint, and then displays you the output in the console.
That console looks exacly like the Azure Cross-Platform Command-Line Interface (xplat-cli) which is based on node.js. I'm not a node.js expert, but a good guees would be, that the browser creates a node.js session und runs the xplat-cli in there.
xplat-cli in turn use the Service Management API of Azure, which are all REST-based.
You can compare the xplat-cli on your own by installing them from the Downloads page. At the bottom of this page are the download links for Windows, Mac, and Linux.
I've recently started using Microsoft Azure and Visual Studio Team Services.
We use VS Team Services for cloud storage of our source repositories in TFS.
Continous deployment is configured to build and deploy on every commit.
As of now, our development environment is public and can be visited by anyone (published to azurewebsites.net)
However, we would like our development environment to be private and not accessible using a userfriendly url. We could implement some authorization on the web site to prevent others seeing our development site, but there must be another way.
There are ways to accomplish this using deployment slots in a staging area (will give me some guid url), but it doesn't seem right.
Is there any built in support to Azure (or Visual Studio Team Services) to accomplish this?
You could leverage domain and / or IP address restrictions to limit who can connect into your host. See: http://azure.microsoft.com/blog/2013/12/09/ip-and-domain-restrictions-for-windows-azure-web-sites/.
I have been looking through the C# and Rest API's for the Microsoft Azure web sites but I cannot find a way of executing the drop box sync command that can be done through the azure portal. Is this possible from an API that any one knows of?
There is support for deploying a WebDeploy file to a Website using PowerShell, so there must be a corresponding API for it.
If you download the publish settings for the website, you'll se that it has a PublishUrl which is the WebDeploy endpoint for the server, along with a msdeploySite, which is your unique site on the server. A WepDeploy file is nothing more than a fancy zip (AFAIK), so by digging into this it should be possible to come up with something which can talk to the webdeploy endpoint and thereby publish.
I don't think that API is something Microsoft publishes though, so you might have to dig deep.
I have been over the documentation, http://msdn.microsoft.com/en-us/library/windowsazure/ee460799.aspx and dont see any reference for Azure Websites?
How do visual studio or Webmatrix deploy the site to Azure Websites? an internal API or did I miss the documentation for deploying a Azure Website from Code?
There's a REST API for websites which is used by Visual Studio and CLI tools behind the scenes however it is not publicly available. One thing you could do is take a look at the source code for CLI tools on Github: https://github.com/WindowsAzure/azure-sdk-tools-xplat and figure out the REST API from there.
I am looking at migrating a dotnetnuke website to Azure. I need both staging and production versions of the site to be running.
I have looked at using Azure Websites, but at the moment there is no support for SSL on custom domains so this can't be used for the production website. I have migrated the staging site to an Azure Website and now have numerous options for publishing updates (ftp, git, using web matrix).
Due to the constraints of Azure Websites, I used the DNN Accelerator to create a cloud service for the production environment. This set up will allow me to have control over IIS and therefore manage SSL certificates (I think).
The problem I have with this is there does not seem to be any publishing options. The only way I can publish is by connecting to the Azure instance via RDP and then copying the website files onto the files system.
Are there any other ways of publishing? I have looked at converting the website to a WAP, but I believe this has implications when it comes to updating to new DNN versions.
You should never publish your application through RDP since these changes are non-persistent (meaning what you published might disappear after a hardware failure / ...). Adding new instances would also mean that these instances don't have the files you published before.
I suggest you start by looking at the DotNetNuke Azure Accelerator first. If this doesn't fit your needs you might always try to build something yourself, but if you want to say with a regular website and not a web application I wouldn't count on Visual Studio support. In that case you might want to look at creating a package from the command line and using startup scripts to add your website in IIS.
Sounds like you need to use a Start-up task to install the files in the correct place for a Web Role (Cloud Service) Smarx has a nice overview here, MSDN has a wealth of info too http://blog.smarx.com/posts/introduction-to-windows-azure-startup-tasks
Another option is IAAS for Azure with a persisted VM, more work mind you, Cloud Service would be the most efficient and correct solution...