Re:The engine for Git push in Azure and for your own server
by OWaz on Friday May 16, 2014 @01:49PM
(#7756753)
The Azure tools don't totally miss out on Cloud Services[1]. You should enter an issue for the commands you feel are missing [2].
[1]: http://azure.microsoft.com/en-us/documentation/articles/comm...
Re:The engine for Git push in Azure and for your own server
by vertex-four on Friday May 16, 2014 @02:35PM
(#7757101)
Sure, I can create one, but how do I push a new deployment to my Cloud Service from Linux? I can create Cloud Services, but I can't deploy anything, as far as I can tell.
Re:The engine for Git push in Azure and for your own server
by blablabla123 on Saturday May 17, 2014 @04:28AM
(#7759589)
>As it turned out, I decided to use node.js on Linux on EC2 instead, as I know that works fine.
Deploying node.js using Linux (or OS X) is actually pretty convenient using Azure Websites. Even though Azure Websites is limited to 10 instances, but until you get 10 instances busy with node.js.....
However I agree, the documentation is horrible. When working with the node drivers for Azure Storage Tables, most of the time I use the source code as doc, fortunately it's well commented.
Re:The engine for Git push in Azure and for your own server
by vertex-four on Saturday May 17, 2014 @07:06AM
(#7759834)
Yeah, I was specifically wanting to use Cloud Services as I have a requirement for long-running background processor nodes, and Cloud Services allows for the creation of those while Websites doesn't.
Re:The engine for Git push in Azure and for your own server
by ahmelsayed on Friday May 16, 2014 @01:45PM
(#7756735)
how long ago was that? I can see it supported now[1] but I don't know if that was something recent or not.
[1] http://azure.microsoft.com/en-us/documentation/articles/comm...
Re:The engine for Git push in Azure and for your own server
by vertex-four on Friday May 16, 2014 @02:37PM
(#7757119)
There's no deployment tools listed there. You can deploy VMs and Azure Websites from Linux, but not Azure Cloud Services.
As it turned out, I decided to use node.js on Linux on EC2 instead, as I know that works fine.
EDIT: Apparently, all the information needed to do this is now public, it's just not exposed in any tools. You need to create a cspkg[0] file and a cscfg[1] file, then use the Create Deployment endpoint[2] to upload them along with extension information.
[0] http://msdn.microsoft.com/en-us/library/jj151532.aspx [1] http://msdn.microsoft.com/en-us/library/ee758710.aspx [2] http://msdn.microsoft.com/en-us/library/azure/ee460813.aspx