tjanczuk/git-azure

Deploy multiple node.js applications to Windows Azure from MacOS using Git

git-azure's Issues

windows: terminal colors are not reverted when git-azure exits

git azure destroy

add blob command

scaffold server.js on git app -name for new apps

null ref in arr.js

git-azure: An uncaught exception was generated by git-azure runtime. Please report it at https://github.com/tjanczuk/git-azure/issues
Thu Jun 14 2012 18:58:23 GMT+0000 (GMT Standard Time)TypeError: Cannot call method 'toLowerCase' of undefined
at loadApp (E:\approot\repo.git-azure\src\runtime\arr.js:792:45)
at Array.onRouteRequest as 0
at Server. (E:\approot\repo.git-azure\src\runtime\node_modules\http-proxy\lib\node-http-proxy.js:174:40)
at Server.emit (events.js:90:17)
at HTTPParser.onIncoming (http.js:1684:12)
at HTTPParser.onHeadersComplete (http.js:115:25)
at Socket.ondata (http.js:1581:22)
at TCP.onread (net.js:388:27)
git-azure: 2012-06-14T18:58:23.083Z Killing existing child processes...
git-azure: Connection to the git-azure management service was unexpectedly terminated. Try refreshing your browser window.

improve error messages on git azure init

When running this:

git azure init --publishSettings ... --servieName .. --username .. --password ..

I get

undefined
  error: unknown option `%s'
undefined

pre-upload node and git to blob to reduce bandwidth costs

windows: git azure init cannot determine the remote url

add enable/disable functionality to an app

consider a custom "site not available" HTML page

windows: npm install -g does not allow 'git azure' to run

when arr.js dies it does not kill its children

this prevents worker role from recycling

SxS support for node versions

Glenn's idea: app store for scaffolding new apps

support configuration & env vars

I would like to have a config.yml scaffolded when creating an app (it should also be added to .gitignore so it does't get added to the repo so we don't disclose keys when using public repos).

The scaffolded .yml file might look like:

# add your own config items that will be accesible using process.env._configkey_

node_env: production

Then we might have a

git azure app --config myapp

That would apply the current config.yml and spawn the env vars for that app on the server.

move arr.js to v0.8 of node

Cannot use libxmljs

I tried deploying a package with a dependency on libxmljs.

If I add the dependency to my package.json and run npm install locally, the app deploys fine, but then when I run it, I get the below error on this line:
require("libxmljs");
//[Error: Cannot find module '../build/default/libxmljs']

If I delete libxmljs from node_modules directory and push, this the output from git push that I get the following npm output:

remote: Running NPM.
remote: npm http GET http://registry.npmjs.org/libxmljs
remote: npm http 200 http://registry.npmjs.org/libxmljs
remote: npm http GET http://registry.npmjs.org/libxmljs/-/libxmljs-0.5.4.tgz
remote: npm http 200 http://registry.npmjs.org/libxmljs/-/libxmljs-0.5.4.tgz
remote: 
remote: > [email protected] install C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\libxmljs
remote: > node-waf configure build
remote: 
remote: 'node-waf' is not recognized as an internal or external command,
remote: operable program or batch file.
remote: 
remote: > [email protected] preuninstall C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\libxmljs
remote: > node-waf clean
remote: 
remote: 'node-waf' is not recognized as an internal or external command,
remote: operable program or batch file.
remote: npm WARN continuing anyway [email protected] preuninstall: `node-waf clean`
remote: npm WARN continuing anyway `cmd "/c" "node-waf clean"` failed with 1
remote: 
remote: npm ERR! [email protected] install: `node-waf configure build`
remote: npm ERR! `cmd "/c" "node-waf configure build"` failed with 1
remote: npm ERR! 
remote: npm ERR! Failed at the [email protected] install script.
remote: npm ERR! This is most likely a problem with the libxmljs package,
remote: npm ERR! not with npm itself.
remote: npm ERR! Tell the author that this fails on your system:
remote: npm ERR!     node-waf configure build
remote: npm ERR! You can get their info via:
remote: npm ERR!     npm owner ls libxmljs
remote: npm ERR! There is likely additional logging output above.
remote: npm ERR! 
remote: npm ERR! System Windows_NT 6.1.7601
remote: npm ERR! command "D:\\Program Files (x86)\\nodejs\\\\node.exe" "D:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
remote: npm ERR! cwd C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot
remote: npm ERR! node -v v0.6.17
remote: npm ERR! npm -v 1.1.21
remote: npm ERR! code ELIFECYCLE
remote: npm ERR! message [email protected] install: `node-waf configure build`
remote: npm ERR! message `cmd "/c" "node-waf configure build"` failed with 1
remote: npm ERR! errno {}
remote: npm ERR! 
remote: npm ERR! Additional logging details can be found in:
remote: npm ERR!     C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\npm-debug.log
remote: SetConsoleTitleW: The operation completed successfully.
remote: 
remote: 
remote: Error - Changes committed to remote repository but your website not updated.

reduce ads

better docs on how to contribute and test

We should add a wiki page explaining how to fork the project and run your own instance of git-azure.

In essence:

• Fork git-azure and do whatever change you want and push to your fork
• Create a test repo to try things
• DON'T run git azure init yet (you want to first add your .git-azure submodule)
• Add your own git-azure submodule git submodule add git@youruser:git-azure .git-azure
• Run git azure init ...
• Pull request :)

The way this works is because git azure init won't bring the original git-azure from https://github.com/tjanczuk/git-azure since there is already a .git-azure folder in your repo, so it will skip that and you will be running with your own

after creating a deployment, wait for it to be running

restart when on an unhandled exception

When the app crashes, it stucks there. We need to restart the app somehow, like forever does.

update readme.md with instructions for hooking up private repos

@woloski, @johnnyhalife, would you mind taking a stab at adding a section about private repos to readme.md since you did the feature?

consider a friendly error when no matching node.js engine found

Currently when a node.js application requires a node.js engine version that is not satisfied by any version installed, arr.js will throw and bring the system down. Diagnostics is not easy (access logs.txt, or you can notice the condition using real time logs if you have them attach at the time of the post receive hook).

This is to disable this application and return a friendly 500 with description for requests targeting this application.

pre-create storage account if none exists

pin the .git-azure submodule to treish corresponding to the CLI version

This is to ensure the version git-azure runtime included in user's repo matches the version of the CLI used.

add less verbose mode for git azure init

prevent deploying private remote URLs

git azure app --delete does not seem to disable path routing

ssh support

support subscription friendly name in addition to guid

clearly display version information such that folks can report it

node v0.6.15 has a problem routing HTTP request after an initial TCP connection

This happens during activation of a node process. Node v0.7.0 does not exhibit the issue.

url path routing

[node.js] Deploy with no node_modules installs dev dependencies

When I deploy a package, devDependencies get installed as well. Below is my package.json file:

{
"author": "Igor Zevaka [email protected]",
"name": "runheat",
"description": "Runkeeper heat map",
"version": "0.0.0-8",
"repository": {
"url": ""
},
"main": "app.js",
"dependencies": {
"express": "2.5.9",
"xml2js": "",
"libxmljs" : "",
"jade": "0.26.1",
"sqlite3": "2.1.1",
"oauth": "0.9.7"
},
"devDependencies": {
"jasmine-node": "1.0.26",
"supervisor": "0.3.3",
"jslint": "0.1.8"
},
"optionalDependencies": {},
"engines": {
"node": "0.6.x"
},
"scripts": {
"pretest": "node_modules/.bin/jslint *.js static/js/script.js --color",
"test": "node_modules/.bin/jasmine-node spec || cat /dev/null",
"start": "node app.js"
},
"subdomain": "runheat"
}

Here is NPM log. Note that dependencies specified in devDependencies get installed as well (Failing in jasmine-node is another issue all together - but it shouldn't be installed in the first place).

remote: New deployment received.
remote: Updating branch 'master'.
remote: ...
remote: Preparing deployment for commit id '343ac20c1d'.
remote: Preparing files for deployment.
remote: Running NPM.
remote: npm http GET http://registry.npmjs.org/xml2js
remote: npm http GET http://registry.npmjs.org/libxmljs
remote: npm http GET http://registry.npmjs.org/jade/0.26.1
remote: npm http GET http://registry.npmjs.org/sqlite3/2.1.1
remote: npm http GET http://registry.npmjs.org/oauth/0.9.7
remote: npm http GET http://registry.npmjs.org/jasmine-node/1.0.26
remote: npm http GET http://registry.npmjs.org/supervisor/0.3.3
remote: npm http GET http://registry.npmjs.org/jslint/0.1.8
remote: npm http GET http://registry.npmjs.org/express/2.5.9
remote: npm http 200 http://registry.npmjs.org/sqlite3/2.1.1
remote: npm http 200 http://registry.npmjs.org/oauth/0.9.7
remote: npm http GET http://registry.npmjs.org/sqlite3/-/sqlite3-2.1.1.tgz
remote: npm http GET http://registry.npmjs.org/oauth/-/oauth-0.9.7.tgz
remote: npm http 200 http://registry.npmjs.org/xml2js
remote: npm http 200 http://registry.npmjs.org/jasmine-node/1.0.26
remote: npm http GET http://registry.npmjs.org/xml2js/-/xml2js-0.1.14.tgz
remote: npm http GET http://registry.npmjs.org/jasmine-node/-/jasmine-node-1.0.26.tgz
remote: npm http 200 http://registry.npmjs.org/jslint/0.1.8
remote: npm http 200 http://registry.npmjs.org/supervisor/0.3.3
remote: npm http GET http://registry.npmjs.org/jslint/-/jslint-0.1.8.tgz
remote: npm http 200 http://registry.npmjs.org/sqlite3/-/sqlite3-2.1.1.tgz
remote: npm http GET http://registry.npmjs.org/supervisor/-/supervisor-0.3.3.tgz
remote: npm http 200 http://registry.npmjs.org/oauth/-/oauth-0.9.7.tgz
remote: npm http 200 http://registry.npmjs.org/express/2.5.9
remote: npm http 200 http://registry.npmjs.org/xml2js/-/xml2js-0.1.14.tgz
remote: npm http GET http://registry.npmjs.org/express/-/express-2.5.9.tgz
remote: npm http 200 http://registry.npmjs.org/jasmine-node/-/jasmine-node-1.0.26.tgz
remote: npm http 200 http://registry.npmjs.org/jslint/-/jslint-0.1.8.tgz
remote: npm http 200 http://registry.npmjs.org/supervisor/-/supervisor-0.3.3.tgz
remote: npm http 200 http://registry.npmjs.org/libxmljs
remote: npm http 200 http://registry.npmjs.org/jade/0.26.1
remote: npm http 200 http://registry.npmjs.org/express/-/express-2.5.9.tgz
remote: npm http GET http://registry.npmjs.org/libxmljs/-/libxmljs-0.5.4.tgz
remote: npm http GET http://registry.npmjs.org/jade/-/jade-0.26.1.tgz
remote: npm http 200 http://registry.npmjs.org/libxmljs/-/libxmljs-0.5.4.tgz
remote: npm http 200 http://registry.npmjs.org/jade/-/jade-0.26.1.tgz
remote: npm WARN excluding symbolic link lib\index.js -> jade.js
remote: npm ERR! error rolling back [email protected] Error: EPERM, stat 'C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\jasmine-node'
remote:
remote: npm ERR! Error: EPERM, stat 'C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\jasmine-node'
remote: npm ERR!
remote: npm ERR! Please try running this command again as root/Administrator.
remote: npm ERR!
remote: npm ERR! System Windows_NT 6.1.7601
remote: npm ERR! command "D:\Program Files (x86)\nodejs\node.exe" "D:\Program Files (x86)\nodejs\node_modules\npm\bin\npm-cli.js" "install"
remote: npm ERR! cwd C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot
remote: npm ERR! node -v v0.6.17
remote: npm ERR! npm -v 1.1.21
remote: npm ERR! path C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\jasmine-node
remote: npm ERR! code EPERM
remote: npm ERR! message EPERM, stat 'C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\jasmine-node'
remote: npm ERR! errno {}
remote: npm ERR! error rolling back [email protected] Error: EPERM, stat 'C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\supervisor'
remote: npm ERR! error rolling back [email protected] Error: EPERM, stat 'C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\oauth'
remote: npm ERR! error rolling back [email protected] Error: EPERM, stat 'C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\express'
remote: npm ERR! error rolling back [email protected] Error: EPERM, stat 'C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\libxmljs'
remote: npm ERR! error rolling back [email protected] Error: EPERM, stat 'C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\xml2js'
remote: npm ERR! error rolling back [email protected] Error: EPERM, stat 'C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\jade'
remote: npm ERR! error rolling back [email protected] Error: EPERM, stat 'C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\sqlite3'
remote: npm ERR! error rolling back [email protected] Error: EPERM, stat 'C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\node_modules\jslint'
remote: npm ERR!
remote: npm ERR! Additional logging details can be found in:
remote: npm ERR! C:\DWASFiles\Sites\runheat2\VirtualDirectory0\site\wwwroot\npm-debug.log
remote: SetConsoleTitleW: The operation completed successfully.
remote:
remote:
remote: Error - Changes committed to remote repository but your website not updated.

multi-instance support

git azure reset

HTTP requests following HTTP requests to the same app fail

This was traced down to http-party/node-http-proxy#248

allow side by side deployments under one subscription

default the blob container name to something derived from service name

Support for https://github.com/c9/azure-packager-node

This way we don't need Windows for repackaging the whole thing (if needed). The idea is to provide an alternative for build.cmd to create the package on non Windows environments

Add support for Azure Affinity Groups

running deployment cannot be deleted

stop deployment before deleting

consider browserless download of publishSettings

windows: does not work due to dependency on openssl

Find a replacement on Windows or disable up front.

add support for npm install

Things to take into account

• Support for multiple apps
• Compat between npm and node engines declared in the app

cc @johnnyhalife

retrieve the storage account keys automatically

git azure status

friendly message on windows

allow setting the azure instance size

add a way to rerun git azure init without loosing the IP

integrate with azure logging

post receive recycle does not pick up configuration changes

Issue is that 'require' caches the JSON of package.json. Use JSON.parse(fs.readFileSync(...)) instead.