Skip to content

Instantly share code, notes, and snippets.

@blakmatrix

blakmatrix/node0.10.0.ps1

Last active December 15, 2015 05:29
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save blakmatrix/5209472 to your computer and use it in GitHub Desktop.
Save blakmatrix/5209472 to your computer and use it in GitHub Desktop.
Download ZIP
jitsu @ 0.12.8
Raw
node0.10.0.ps1
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.
PS C:\Users\fred rosak> cd c:/jitsu
PS C:\jitsu> node -v
v0.10.0
PS C:\jitsu> npm -v
1.2.14
PS C:\jitsu> npm test
> jitsu@0.12.8 test C:\jitsu
> vows test/commands/*-test.js test/lib/*-test.js --spec -i
♢ jitsu/commands/apps
apps list
✓ should respond with no error
apps list
✓ should prompt for credentials
apps view application2
✓ should respond with no error
apps view application2
✓ should prompt for credentials
apps start application3
✓ should respond with no error
apps start application3
✓ should prompt for credentials
apps stop application3
✓ should respond with no error
apps stop application3
✓ should prompt for credentials
apps view
✓ should respond with no error
apps start
✓ should respond with no error
apps stop
✓ should respond with no error
error: The subdomain requested is already in use
apps deploy
✓ should respond with no error
error: Error: Invalid package.json file
error: Please make sure C:\jitsu\test\fixtures\example-app\package.json is valid JSON
error: Error running command apps deploy
apps deploy
✓ should display an error on broken package.json
cloud example-app
✓ should show cloud info
cloud
✓ should show cloud info
cloud joyent
✓ should show cloud info
cloud example-app joyent
✓ should respond with no error
error: Error starting example-app
error: Error running command cloud example-app unknow-provider somedc
error: Unknown cloud: unknow-provider somedc
error: Error: Unknown cloud: unknow-provider somedc
error: at iterate (C:\jitsu\node_modules\nodejitsu-api\lib\client\client.js:114:21)
error: at loop (C:\jitsu\node_modules\nodejitsu-api\lib\client\helpers.js:63:7)
error: at Array.forEach (native)
error: at Object.map (C:\jitsu\node_modules\nodejitsu-api\lib\client\helpers.js:62:9)
error: at completed (C:\jitsu\node_modules\nodejitsu-api\lib\client\client.js:103:11)
error: at Object.iterate (C:\jitsu\node_modules\nodejitsu-api\lib\client\helpers.js:35:27)
error: at Client.cloud (C:\jitsu\node_modules\nodejitsu-api\lib\client\client.js:99:9)
error: at executeCloud (C:\jitsu\node_modules\nodejitsu-api\lib\client\apps.js:237:10)
error: at C:\jitsu\node_modules\nodejitsu-api\lib\client\apps.js:232:7
error: at C:\jitsu\node_modules\nodejitsu-api\lib\client\apps.js:85:5
cloud example-app unknow-provider somedc
✓ should fail
♢ jitsu/commands/malformed
app list
✓ should exit gracefully
apps derploy
✓ should exit gracefully
env lost
✓ should exit gracefully
error: Sorry, socketio is not a node app
♢ jitsu/commands/databases
databases list
✓ should respond with no error
databases list
✓ should prompt for credentials
databases get test
✓ should respond with no error
databases get test
✓ should prompt for credentials
databases create couch test2
✓ should respond with no error
error: Database name is required
databases create
✓ should respond with no error
databases create couch test4
✓ should prompt for credentials
databases destroy test3
✓ should respond with no error
♢ jitsu/commands/env
env list
✓ should respond with no error
env list
✓ should prompt for credentials
env list foobar
✓ should respond with no error
env list barbaz
✓ should respond with no error
env get foo
✓ should respond with no error
env get foo
✓ should prompt for credentials
env get barbaz ping
✓ should respond with no error
error: Environment variable name and value and both required
error: Error running command env set
env set
✓ Should exit with an error
env set test truthy
✓ should respond with no error
env set test truthy
✓ should prompt for credentials
env set barbaz delete test
✓ should respond with no error
env set delete test
✓ should respond with no error
env delete delete
✓ should respond with no error
env delete delete
✓ should prompt for credentials
env delete barbaz delete
✓ should respond with no error
env clear
✓ The current app should have an empty env
env clear barbaz
✓ The specified app should have an empty env
env save
✓ The current app should save enviroment variables
env save barbaz
✓ The specified app should save enviroment variables
env save env_vars.json
✓ The current app should save enviroment variables to the specified filename
env save barbaz env_vars.json
✓ The specified app should save enviroment variables to the specified filename
env load
✓ The current app should load enviroment variables from env.json
env load barbaz
✓ The specified app should load enviroment variables from env.json
env load env_vars.json
✓ The current app should load enviroment variables from the specified file
♢ jitsu/commands/logs
logs
✓ should respond with no error
logs
✓ should prompt for credentials
logs app
✓ should respond with no error
logs app
✓ should prompt for credentials
logs app application
✓ should respond with no error
logs app application
✓ should prompt for credentials
♢ jitsu/commands/no-colors
♢ jitsu/commands/package
♢ jitsu/commands/snapshots
snapshots list application
✓ should respond with no error
snapshots list application
✓ should prompt for credentials
snapshots list application2
✓ should respond with no error
snapshots activate application2
✓ should prompt for credentials
snapshots activate application2
✓ should respond with no error
snapshots activate application2
✓ should prompt for credentials
snapshots destroy application3
✓ should respond with no error
snapshots destroy application3
✓ should prompt for credentials
snapshots list
✓ should respond with no error
snapshots activate
✓ should respond with no error
♢ jitsu/commands/tokens
tokens list
✓ should respond with no error
tokens list adam
✓ should respond with no error
tokens create
✓ should respond with no error
tokens create test-token
✓ should respond with no error
tokens list
✓ should respond with no error
tokens destroy test-token
✓ should respond with no error
tokens create adam test-token
✓ should respond with no error
tokens list adam
✓ should respond with no error
♢ jitsu/commands/users
error: Error running command users confirm jimmy
error: Nodejitsu Error (400): Bad Request
users confirm jimmy
✓ should respond with a 400 error
♢ jitsu/lib/package
✗ Errored » 11 errored (0.000s)
npm ERR! Test failed. See above for more details.
npm ERR! not ok code 0
PS C:\jitsu> vows test/lib/*-test.js --spec -i
♢ jitsu/lib/package
✗ Errored » 1 errored (0.000s)
PS C:\jitsu> node .\test\lib\package-test.js
·················warn: **WARNING** Do not use multiple level subdomains, they will be going away soon!
······· ✓ OK » 24 honored (0.074s)
PS C:\jitsu> node .\test\lib\package-test.js --debug
·················warn: **WARNING** Do not use multiple level subdomains, they will be going away soon!
······· ✓ OK » 24 honored (0.029s)
PS C:\jitsu> node .\test\commands\no-colors-test.js
✗ Errored » callback not fired
in when using the --no-colors flag
in jitsu/commands/no-colors
in undefined✗ Errored » 1 errored ∙ 1 dropped
PS C:\jitsu> node .\test\commands\package-test.js
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command package create
info: Skipping require-analyzer because noanalyze option is set
info: Creating tarball for example-app
info: Tarball for example-app at C:\Users\fred rosak\.jitsu\tmp\tester-example-app-0.0.0-1.tgz
· ✓ OK » 1 honored (0.323s)
PS C:\jitsu> node .\test\commands\users-test.js
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command users confirm jimmy
info: Confirming user jimmy
error: Error running command users confirm jimmy
error: Nodejitsu Error (400): Bad Request
help: For help with this error contact Nodejitsu Support:
help: webchat: <http://webchat.nodejitsu.com/>
help: irc: <irc://chat.freenode.net/#nodejitsu>
help: email: <support@nodejitsu.com>
help:
help: Copy and paste this output to a gist (http://gist.github.com/)
info: Nodejitsu not ok
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command users confirm elvis
info: Confirming user elvis
info: Great success! elvis is now confirmed.
info: User elvis confirmed
info: Log in now?
· ✓ OK » 2 honored (0.420s)
PS C:\jitsu> node .\test\commands\apps-test.js
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps list
info: Listing all apps for tester
data: name state subdomain drones running snapshot
data: application stopped application undefined/undefined ---
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps list
info: Listing all apps for tester
data: name state subdomain drones running snapshot
data: application stopped application undefined/undefined ---
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps view application2
info: Viewing app application2
data: {
data: ctime: '03/20 16:50:30 PDT',
data: mtime: '03/20 16:50:30 PDT',
data: name: 'application2',
data: scripts: { start: './server.js' },
data: snapshots: [
data: { id: '0.0.0', created: '02/13 15:31:38 PST' }
data: ],
data: state: 'stopped',
data: subdomain: 'application2'
data: }
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps view application2
info: Viewing app application2
data: {
data: ctime: '03/20 16:50:31 PDT',
data: mtime: '03/20 16:50:31 PDT',
data: name: 'application2',
data: scripts: { start: './server.js' },
data: snapshots: [
data: { id: '0.0.0', created: '02/13 15:31:38 PST' }
data: ],
data: state: 'stopped',
data: subdomain: 'application2'
data: }
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps start application3
info: Starting app application3
info: App application3 is now started
info: http://application3.jit.su on Port 80
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps start application3
info: Starting app application3
info: App application3 is now started
info: http://application3.jit.su on Port 80
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps stop application3
info: Stopping app application3
info: App application3 is now stopped
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps stop application3
info: Stopping app application3
info: App application3 is now stopped
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps view
info: Attempting to view app C:\jitsu\test\fixtures\example-app/package.json
info: Viewing app example-app
data: {
data: ctime: '03/20 16:50:32 PDT',
data: mtime: '03/20 16:50:32 PDT',
data: name: 'application',
data: scripts: { start: './server.js' },
data: snapshots: [
data: { id: '0.0.0-1', created: '02/13 15:31:38 PST' }
data: ],
data: state: 'stopped',
data: subdomain: 'application'
data: }
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps start
info: Starting app example-app
info: App example-app is now started
info: http://example-app.jit.su on Port 80
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps stop
info: Stopping app example-app
info: App example-app is now stopped
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps deploy
info: Analyzing application dependencies in server.js
info: Checking app availability example-app
error: The subdomain requested is already in use
info: Checking app availability example-app
info: Creating app example-app
info: Creating snapshot 0.0.0
info: Updating app example-app
info: Activating snapshot 0.0.0 for example-app
info: Starting app example-app
info: App example-app is now started
info: http://example-app.jit.su on Port 80
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps deploy
error: Error: Invalid package.json file
error: Please make sure C:\jitsu\test\fixtures\example-app\package.json is valid JSON
error: Error running command apps deploy
help: For help with this error contact Nodejitsu Support:
help: webchat: <http://webchat.nodejitsu.com/>
help: irc: <irc://chat.freenode.net/#nodejitsu>
help: email: <support@nodejitsu.com>
help:
help: Copy and paste this output to a gist (http://gist.github.com/)
info: Nodejitsu not ok
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command cloud example-app
info: Fetching app example-app
info: Viewing cloud info for example-app
data: {
data: datacenter: 'us-east-1',
data: drones: 2,
data: provider: 'joyent'
data: }
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command cloud
info: Fetching app example-app
info: Viewing cloud info for example-app
data: {
data: datacenter: 'us-east-1',
data: drones: 2,
data: provider: 'joyent'
data: }
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command cloud joyent
info: Fetching app example-app
info: Viewing cloud info for example-app
data: {
data: datacenter: 'us-east-1',
data: drones: 2,
data: provider: 'joyent'
data: }
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command cloud example-app joyent
info: Fetching app example-app
info: Viewing cloud info for example-app
data: {
data: datacenter: 'us-east-1',
data: drones: 2,
data: provider: 'joyent'
data: }
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command cloud example-app unknow-provider somedc
info: Fetching app example-app
info: Deploying application to the cloud with:
data: {
data: datacenter: 'somedc',
data: drones: 2,
data: provider: 'unknow-provider',
data: ram: undefined
data: }
error: Error starting example-app
error: Error running command cloud example-app unknow-provider somedc
error: Unknown cloud: unknow-provider somedc
error: Error: Unknown cloud: unknow-provider somedc
error: at iterate (C:\jitsu\node_modules\nodejitsu-api\lib\client\client.js:114:21)
error: at loop (C:\jitsu\node_modules\nodejitsu-api\lib\client\helpers.js:63:7)
error: at Array.forEach (native)
error: at Object.map (C:\jitsu\node_modules\nodejitsu-api\lib\client\helpers.js:62:9)
error: at completed (C:\jitsu\node_modules\nodejitsu-api\lib\client\client.js:103:11)
error: at Object.iterate (C:\jitsu\node_modules\nodejitsu-api\lib\client\helpers.js:35:27)
error: at Client.cloud (C:\jitsu\node_modules\nodejitsu-api\lib\client\client.js:99:9)
error: at executeCloud (C:\jitsu\node_modules\nodejitsu-api\lib\client\apps.js:237:10)
error: at C:\jitsu\node_modules\nodejitsu-api\lib\client\apps.js:232:7
error: at C:\jitsu\node_modules\nodejitsu-api\lib\client\apps.js:85:5
help: For help with this error contact Nodejitsu Support:
help: webchat: <http://webchat.nodejitsu.com/>
help: irc: <irc://chat.freenode.net/#nodejitsu>
help: email: <support@nodejitsu.com>
help:
help: Copy and paste this output to a gist (http://gist.github.com/)
info: Nodejitsu not ok
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command cloud list
info: You can use one of the following providers
data: jitsu cloud joyent us-east-1
· ✓ OK » 19 honored (3.621s)
PS C:\jitsu> node .\test\commands\bad-test.js
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command app list
help: ___ __
help: / / / /_ / /
help: __/ / / __/ /__/
help:
help: Flawless deployment of Node.js apps to the cloud
help: open-source and fully customizable.
help: https://github.com/nodejitsu/jitsu
help:
help: Usage:
help:
help: jitsu <resource> <action> <param1> <param2> ...
help:
help: Common Commands:
help:
help: To sign up for Nodejitsu
help: jitsu signup
help:
help: To log into Nodejitsu
help: jitsu login
help:
help: To install a pre-built application
help: jitsu install
help:
help: Deploys current path to Nodejitsu
help: jitsu deploy
help:
help: Lists all applications for the current user
help: jitsu list
help:
help: Additional Commands
help: jitsu apps
help: jitsu cloud
help: jitsu logs
help: jitsu env
help: jitsu conf
help: jitsu users
help: jitsu databases
help: jitsu snapshots
help: jitsu tokens
help: jitsu logout
help:
help: Options:
help: --version, -v print jitsu version and exit [string]
help: --localconf search for .jitsuconf file in ./ and then parent directories [string]
help: --jitsuconf, -j specify file to load configuration from [string]
help: --noanalyze skip require-analyzer: do not attempt to dynamically detect dependencies [boolean]
help: --colors --no-colors will disable output coloring [boolean] [default: true]
help: --confirm, -c prevents jitsu from asking before overwriting/removing things [boolean] [default: false]
help: --release, -r specify release version number or semantic increment (build, patch, minor, major) [string]
help: --raw jitsu will only output line-delimited raw JSON (useful for piping) [boolean]
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command apps derploy
help: The `jitsu apps` command manages
help: Applications on Nodejitsu. Valid commands are:
help:
help: jitsu apps deploy
help: jitsu apps list
help: jitsu apps create
help: jitsu apps cloud [<name>]
help: jitsu apps view [<name>]
help: jitsu apps update [<name>]
help: jitsu apps destroy [<name>]
help: jitsu apps start [<name>]
help: jitsu apps restart [<name>]
help: jitsu apps stop [<name>]
help: jitsu apps setdrones [<name>] <number>
help:
help: For commands that take a <name> parameter, if no parameter
help: is supplied, jitsu will attempt to read the package.json
help: from the current directory.
help:
help: Options:
help: --version, -v print jitsu version and exit [string]
help: --localconf search for .jitsuconf file in ./ and then parent directories [string]
help: --jitsuconf, -j specify file to load configuration from [string]
help: --noanalyze skip require-analyzer: do not attempt to dynamically detect dependencies [boolean]
help: --colors --no-colors will disable output coloring [boolean] [default: true]
help: --confirm, -c prevents jitsu from asking before overwriting/removing things [boolean] [default: false]
help: --release, -r specify release version number or semantic increment (build, patch, minor, major) [string]
help: --raw jitsu will only output line-delimited raw JSON (useful for piping) [boolean]
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env lost
help: `jitsu env *` commands enable management of environment
help: variables for the app. Valid commands are:
help:
help: jitsu env list
help: jitsu env list <app>
help: jitsu env set <key> <value>
help: jitsu env get <key>
help: jitsu env delete <key>
help: jitsu env clear
help: jitsu env save [<app>] [<file>]
help: jitsu env load [<app>] [<file>]
help:
help: Options:
help: --version, -v print jitsu version and exit [string]
help: --localconf search for .jitsuconf file in ./ and then parent directories [string]
help: --jitsuconf, -j specify file to load configuration from [string]
help: --noanalyze skip require-analyzer: do not attempt to dynamically detect dependencies [boolean]
help: --colors --no-colors will disable output coloring [boolean] [default: true]
help: --confirm, -c prevents jitsu from asking before overwriting/removing things [boolean] [default: false]
help: --release, -r specify release version number or semantic increment (build, patch, minor, major) [string]
help: --raw jitsu will only output line-delimited raw JSON (useful for piping) [boolean]
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command install socketio
error: Sorry, socketio is not a node app
error: Error running command install socketio
help: For help with this error contact Nodejitsu Support:
help: webchat: <http://webchat.nodejitsu.com/>
help: irc: <irc://chat.freenode.net/#nodejitsu>
help: email: <support@nodejitsu.com>
help:
help: Copy and paste this output to a gist (http://gist.github.com/)
info: Nodejitsu not ok
· ✓ OK » 4 honored (0.965s)
PS C:\jitsu> node .\test\commands\databases-test.js
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command databases list
info:
data: Database Type: couch
data: Database Name: test
data: Connection url: http://nodejitsudb951231780457.iriscouch.com:5984
data: SSL connection url: https://nodejitsudb951231780457.iriscouch.com:6984
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command databases list
info:
data: Database Type: couch
data: Database Name: test
data: Connection url: http://nodejitsudb951231780457.iriscouch.com:5984
data: SSL connection url: https://nodejitsudb951231780457.iriscouch.com:6984
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command databases get test
data: Database Type: couch
data: Database Name: test
data: Connection url: http://nodejitsudb951231780457.iriscouch.com:5984
data: SSL connection url: https://nodejitsudb951231780457.iriscouch.com:6984
help:
help: Connect with `curl`:
help:
$ curl http://nodejitsudb951231780457.iriscouch.com:5984
help:
help: Connect with the `futon` web app (open in a web browser):
help:
http://nodejitsudb951231780457.iriscouch.com:5984/_utils
help:
help: Connect with the `nano` module:
help:
var nano = require('nano')('http://nodejitsudb951231780457.iriscouch.com:5984');
help:
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command databases get test
data: Database Type: couch
data: Database Name: test
data: Connection url: http://nodejitsudb951231780457.iriscouch.com:5984
data: SSL connection url: https://nodejitsudb951231780457.iriscouch.com:6984
help:
help: Connect with `curl`:
help:
$ curl http://nodejitsudb951231780457.iriscouch.com:5984
help:
help: Connect with the `futon` web app (open in a web browser):
help:
http://nodejitsudb951231780457.iriscouch.com:5984/_utils
help:
help: Connect with the `nano` module:
help:
var nano = require('nano')('http://nodejitsudb951231780457.iriscouch.com:5984');
help:
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command databases create couch test2
info: A new couch has been created
data: Database Type: couch
data: Database Name: test2
data: Connection url: http://nodejitsudb951231780457.iriscouch.com:5984
data: SSL connection url: https://nodejitsudb951231780457.iriscouch.com:6984
help:
help: Connect with `curl`:
help:
$ curl http://nodejitsudb951231780457.iriscouch.com:5984
help:
help: Connect with the `futon` web app (open in a web browser):
help:
http://nodejitsudb951231780457.iriscouch.com:5984/_utils
help:
help: Connect with the `nano` module:
help:
var nano = require('nano')('http://nodejitsudb951231780457.iriscouch.com:5984');
help:
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command databases create
warn: Valid database types are: couch (iriscouch), redis (irisredis), mongo (mongolab), mongohq, orredistogo
error: Database name is required
info: A new mongo has been created
data: Database Type: mongo
data: Database Name: test3
data: Connection url: mongo://nodejitsu:pass@this.is.only.a.test.mongohq.com:10039//path
help:
help: Connect with the `mongo` cli client:
help:
$ mongo this.is.only.a.test.mongohq.com:10039//path -u nodejitsu -p pass
help:
help: Connect with the `mongodb-native module`:
help:
var mongodb = require('mongodb');
var db = new mongodb.Db('/path',
new mongodb.Server('this.is.only.a.test.mongohq.com', 10039, {})
);
db.open(function (err, db_p) {
if (err) { throw err; }
db.authenticate('nodejitsu', 'pass', function (err, replies) {
// You are now connected and authenticated.
});
});
help:
help: Connect with the `mongoose` module:
help:
var mongoose = require('mongoose');
mongoose.connect('mongo://nodejitsu:pass@this.is.only.a.test.mongohq.com:10039//path');
help:
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command databases create couch test4
info: A new couch has been created
data: Database Type: couch
data: Database Name: test4
data: Connection url: http://nodejitsudb951231780457.iriscouch.com:5984
data: SSL connection url: https://nodejitsudb951231780457.iriscouch.com:6984
help:
help: Connect with `curl`:
help:
$ curl http://nodejitsudb951231780457.iriscouch.com:5984
help:
help: Connect with the `futon` web app (open in a web browser):
help:
http://nodejitsudb951231780457.iriscouch.com:5984/_utils
help:
help: Connect with the `nano` module:
help:
var nano = require('nano')('http://nodejitsudb951231780457.iriscouch.com:5984');
help:
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command databases destroy test3
info: Database was deleted
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command databases destroy test4
info: Database was deleted
· ✓ OK » 9 honored (1.718s)
PS C:\jitsu> node .\test\commands\env-test.js
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env list
info: Attempting to load env variables for app C:\jitsu/package.json
info: Listing all environment variables for application
data: { baz: 'buzz', foo: 'bar' }
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env list
info: Attempting to load env variables for app C:\jitsu/package.json
info: Listing all environment variables for application
data: { baz: 'buzz', foo: 'bar' }
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env list foobar
info: Listing all environment variables for application
data: { baz: 'buzz', foo: 'bar' }
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env list barbaz
info: Listing all environment variables for barbaz
data: { ping: 'fizz', pong: 'buzz' }
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env get foo
info: Attempting to load env variables for app C:\jitsu/package.json
data: foo bar
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env get foo
info: Attempting to load env variables for app C:\jitsu/package.json
data: foo bar
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env get barbaz ping
data: ping fizz
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env set
error: Environment variable name and value and both required
error: Error running command env set
help: For help with this error contact Nodejitsu Support:
help: webchat: <http://webchat.nodejitsu.com/>
help: irc: <irc://chat.freenode.net/#nodejitsu>
help: email: <support@nodejitsu.com>
help:
help: Copy and paste this output to a gist (http://gist.github.com/)
info: Nodejitsu not ok
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env set test truthy
info: Attempting to load env variables for app C:\jitsu/package.json
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env set test truthy
info: Attempting to load env variables for app C:\jitsu/package.json
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env set barbaz delete test
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env set delete test
info: Attempting to load env variables for app C:\jitsu/package.json
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env delete delete
info: Attempting to load env variables for app C:\jitsu/package.json
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env delete delete
info: Attempting to load env variables for app C:\jitsu/package.json
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env delete barbaz delete
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env clear
info: Attempting to load env variables for app C:\jitsu/package.json
warn: All environment variables for application will be deleted.
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env clear barbaz
warn: All environment variables for barbaz will be deleted.
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env save
info: Attempting to load env variables for app C:\jitsu/package.json
info: Saving all environment variables for application to env.json
warn: This may contain sensitive data. Be sure not to commit this file to some public repository. YOU HAVE BEEN WARNED.
info: Is this okay?
info: env.json written!
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env save barbaz
info: Saving all environment variables for barbaz to env.json
warn: This may contain sensitive data. Be sure not to commit this file to some public repository. YOU HAVE BEEN WARNED.
info: Is this okay?
info: env.json written!
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env save env_vars.json
info: Attempting to load env variables for app C:\jitsu/package.json
info: Saving all environment variables for application to env_vars.json
warn: This may contain sensitive data. Be sure not to commit this file to some public repository. YOU HAVE BEEN WARNED.
info: Is this okay?
info: env_vars.json written!
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env save barbaz env_vars.json
info: Saving all environment variables for barbaz to env_vars.json
warn: This may contain sensitive data. Be sure not to commit this file to some public repository. YOU HAVE BEEN WARNED.
info: Is this okay?
info: env_vars.json written!
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env load
info: Attempting to load env variables for app C:\jitsu/package.json
info: Replacing all environment variables for application from variables in env.json
info: Old environment variables:
data: {
data: baz: 'buzz',
data: foo: 'bar',
data: test: 'truthy'
data: }
info: New environment variables:
data: {
data: baz: 'buzz',
data: foo: 'bar',
data: test: 'truthy1'
data: }
warn: YOU CAN LOSE ENVIRONMENT VARIABLES IF YOU ARE NOT CAREFUL.
info: Is this okay?
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env load barbaz
info: Replacing all environment variables for barbaz from variables in env.json
info: Old environment variables:
data: {
data: baz: 'buzz',
data: foo: 'bar',
data: test: 'truthy'
data: }
info: New environment variables:
data: {
data: baz: 'buzz',
data: foo: 'bar',
data: test: 'truthy1'
data: }
warn: YOU CAN LOSE ENVIRONMENT VARIABLES IF YOU ARE NOT CAREFUL.
info: Is this okay?
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env load env_vars.json
info: Attempting to load env variables for app C:\jitsu/package.json
info: Replacing all environment variables for application from variables in env_vars.json
info: Old environment variables:
data: {
data: baz: 'buzz',
data: foo: 'bar',
data: test: 'truthy1'
data: }
info: New environment variables:
data: {
data: baz: 'buzz',
data: foo: 'bar',
data: test: 'truthy2'
data: }
warn: YOU CAN LOSE ENVIRONMENT VARIABLES IF YOU ARE NOT CAREFUL.
info: Is this okay?
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command env load barbaz env_vars.json
info: Replacing all environment variables for barbaz from variables in env_vars.json
info: Old environment variables:
data: {
data: baz: 'buzz',
data: foo: 'bar',
data: test: 'truthy1'
data: }
info: New environment variables:
data: {
data: baz: 'buzz',
data: foo: 'bar',
data: test: 'truthy2'
data: }
warn: YOU CAN LOSE ENVIRONMENT VARIABLES IF YOU ARE NOT CAREFUL.
info: Is this okay?
· · ✓ OK » 26 honored (4.432s)
PS C:\jitsu> node .\test\commands\logs-test.js
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command logs app
info: Attempting to load logs for C:\jitsu\test\fixtures\example-app/package.json
info: Listing logs for example-app
[12/20 16:00:00 PST] This is a message
[12/20 17:00:00 PST] This is also a message
[12/20 18:00:00 PST] This is a message on stderr
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command logs app
info: Attempting to load logs for C:\jitsu\test\fixtures\example-app/package.json
info: Listing logs for example-app
[12/20 16:00:00 PST] This is a message
[12/20 17:00:00 PST] This is also a message
[12/20 18:00:00 PST] This is a message on stderr
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command logs app
info: Attempting to load logs for C:\jitsu\test\fixtures\example-app/package.json
info: Listing logs for example-app
[12/20 16:00:00 PST] This is a message
[12/20 17:00:00 PST] This is also a message
[12/20 18:00:00 PST] This is a message on stderr
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command logs app
info: Attempting to load logs for C:\jitsu\test\fixtures\example-app/package.json
info: Listing logs for example-app
[12/20 16:00:00 PST] This is a message
[12/20 17:00:00 PST] This is also a message
[12/20 18:00:00 PST] This is a message on stderr
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command logs app application
info: Listing logs for application
[12/20 16:00:00 PST] This is a message
[12/20 17:00:00 PST] This is also a message
[12/20 18:00:00 PST] This is a message on stderr
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command logs app application
info: Listing logs for application
[12/20 16:00:00 PST] This is a message
[12/20 17:00:00 PST] This is also a message
[12/20 18:00:00 PST] This is a message on stderr
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command logs app application 10
info: Listing logs for application
[12/20 16:00:00 PST] This is a message
[12/20 17:00:00 PST] This is also a message
[12/20 18:00:00 PST] This is a message on stderr
· ✓ OK » 7 honored (1.344s)
PS C:\jitsu> node .\test\commands\snapshots-test.js
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command snapshots list application
info: Listing snapshots for application
data: name status created md5
data: 0.0.0 archived 03/20 16:51:35 PDT q34rq43r5t5g4w56t45t
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command snapshots list application
info: Listing snapshots for application
data: name status created md5
data: 0.0.0 archived 03/20 16:51:36 PDT q34rq43r5t5g4w56t45t
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command snapshots list application2
info: Listing snapshots for application2
data: name status created md5
data: 0.0.0 archived 03/20 16:51:36 PDT q34rq43r5t5g4w56t45t
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command snapshots activate application2
info: Listing snapshots for application2
data: name status created md5
data: 0.0.0-1 archived 03/20 16:51:36 PDT q34rq43r5t5g4w56t45t
info: Activating snapshot 0.0.0-1
info: Snapshot 0.0.0-1 is now active
info: Starting app application2
info: App application2 is now started
info: http://tester.application2.jit.su on Port 80
info: Snapshot 0.0.0-1 is now running
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command snapshots activate application2
info: Listing snapshots for application2
data: name status created md5
data: 0.0.0-1 archived 03/20 16:51:36 PDT q34rq43r5t5g4w56t45t
info: Activating snapshot 0.0.0-1
info: Snapshot 0.0.0-1 is now active
info: Starting app application2
info: App application2 is now started
info: http://tester.application2.jit.su on Port 80
info: Snapshot 0.0.0-1 is now running
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command snapshots activate application2
info: Listing snapshots for application2
data: name status created md5
data: 0.0.0-1 archived 03/20 16:51:36 PDT q34rq43r5t5g4w56t45t
info: Activating snapshot 0.0.0-1
info: Snapshot 0.0.0-1 is now active
info: Starting app application2
info: App application2 is now started
info: http://tester.application2.jit.su on Port 80
info: Snapshot 0.0.0-1 is now running
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command snapshots destroy application3
info: Listing snapshots for application3
data: name status created md5
data: 0.0.0-1 archived 03/20 16:51:37 PDT q34rq43r5t5g4w56t45t
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command snapshots destroy application3
info: Listing snapshots for application3
data: name status created md5
data: 0.0.0-1 archived 03/20 16:51:37 PDT q34rq43r5t5g4w56t45t
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command snapshots list
info: Attempting to load snapshots for C:\jitsu\test\fixtures\example-app/package.json
info: Listing snapshots for example-app
data: name status created md5
data: 0.0.0 archived 03/20 16:51:37 PDT q34rq43r5t5g4w56t45t
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command snapshots activate
info: Attempting to load snapshots for C:\jitsu\test\fixtures\example-app/package.json
info: Listing snapshots for example-app
data: name status created md5
data: 0.0.0-1 archived 03/20 16:51:37 PDT q34rq43r5t5g4w56t45t
info: Activating snapshot 0.0.0-1
info: Snapshot 0.0.0-1 is now active
info: Starting app example-app
info: App example-app is now started
info: http://tester.example-app.jit.su on Port 80
info: Snapshot 0.0.0-1 is now running
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command snapshots destroy
info: Listing snapshots for example-app
data: name status created md5
data: 0.0.0-1 archived 03/20 16:51:37 PDT q34rq43r5t5g4w56t45t
· ✓ OK » 11 honored (1.991s)
PS C:\jitsu> node .\test\commands\tokens-test.js
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command tokens list
info: Listing all tokens for tester
warn: No tokens exist.
help: Try creating one with jitsu tokens create
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command tokens list adam
info: Listing all tokens for adam
warn: No tokens exist.
help: Try creating one with jitsu tokens create
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command tokens create
info: Creating a token for tester
info: Token Created:
data: undefined : undefined
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command tokens create test-token
info: Creating a token for tester
info: Token Created:
data: undefined : undefined
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command tokens list
info: Listing all tokens for tester
data: name token
data: test-token bbe261ea-aa43-4f6d-a3cf-b971301d459b
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command tokens destroy test-token
info: Deleting token test-token for tester
info: Token test-token Destroyed!
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command tokens create adam test-token
info: Creating a token for adam
info: Token Created:
data: undefined : undefined
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command tokens list adam
info: Listing all tokens for adam
data: name token
data: test-token bbe261ea-aa43-4f6d-a3cf-b971301d459b
·
info: Welcome to Nodejitsu tester
info: jitsu v0.12.8, node v0.10.0
info: It worked if it ends with Nodejitsu ok
info: Executing command tokens destroy adam test-token
info: Deleting token test-token for adam
info: Token test-token Destroyed!
· ✓ OK » 9 honored (1.672s)
PS C:\jitsu>
Raw
node0.6.21.ps1
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.
PS C:\Users\fred rosak> cd c:/jitsu
PS C:\jitsu> node -v
v0.6.21-pre
PS C:\jitsu> npm -v
1.1.37
PS C:\jitsu> vows -v
vows bin argv []
vows bin options {
reporter: 'dot-matrix',
matcher: /.*/
}
vows bin discovering folder structure
vows bin discovered ./test
vows runner loading [
'C:\\jitsu\\test\\commands\\apps-test',
'C:\\jitsu\\test\\commands\\bad-test',
'C:\\jitsu\\test\\commands\\databases-test',
'C:\\jitsu\\test\\commands\\env-test',
'C:\\jitsu\\test\\commands\\logs-test',
'C:\\jitsu\\test\\commands\\no-colors-test',
'C:\\jitsu\\test\\commands\\package-test',
'C:\\jitsu\\test\\commands\\snapshots-test',
'C:\\jitsu\\test\\commands\\tokens-test',
'C:\\jitsu\\test\\commands\\users-test',
'C:\\jitsu\\test\\lib\\package-test'
]
0.12.8
PS C:\jitsu>
PS C:\jitsu>
PS C:\jitsu> npm test
> jitsu@0.12.8 test C:\jitsu
> vows test/commands/*-test.js test/lib/*-test.js --spec -i
♢ jitsu/commands/apps
apps list
✓ should respond with no error
apps list
✓ should prompt for credentials
apps view application2
✓ should respond with no error
apps view application2
✓ should prompt for credentials
apps start application3
✓ should respond with no error
apps start application3
✓ should prompt for credentials
apps stop application3
✓ should respond with no error
apps stop application3
✓ should prompt for credentials
apps view
✓ should respond with no error
apps start
✓ should respond with no error
apps stop
✓ should respond with no error
error: The subdomain requested is already in use
apps deploy
✓ should respond with no error
error: Error: Invalid package.json file
error: Please make sure C:\jitsu\test\fixtures\example-app\package.json is valid JSON
apps deploy
✓ should display an error on broken package.json
error: Error running command apps deploy
cloud example-app
✓ should show cloud info
cloud
✓ should show cloud info
cloud joyent
✓ should show cloud info
cloud example-app joyent
✓ should respond with no error
error: Error starting example-app
error: Error running command cloud example-app unknow-provider somedc
cloud example-app unknow-provider somedc
✓ should fail
error: Unknown cloud: unknow-provider somedc
error: Error: Unknown cloud: unknow-provider somedc
error: at iterate (C:\jitsu\node_modules\nodejitsu-api\lib\client\client.js:114:21)
error: at loop (C:\jitsu\node_modules\nodejitsu-api\lib\client\helpers.js:63:7)
error: at Array.forEach (native)
error: at Object.map (C:\jitsu\node_modules\nodejitsu-api\lib\client\helpers.js:62:9)
error: at completed (C:\jitsu\node_modules\nodejitsu-api\lib\client\client.js:103:11)
error: at Object.iterate (C:\jitsu\node_modules\nodejitsu-api\lib\client\helpers.js:35:27)
error: at [object Object].cloud (C:\jitsu\node_modules\nodejitsu-api\lib\client\client.js:99:9)
error: at executeCloud (C:\jitsu\node_modules\nodejitsu-api\lib\client\apps.js:237:10)
error: at C:\jitsu\node_modules\nodejitsu-api\lib\client\apps.js:232:7
error: at C:\jitsu\node_modules\nodejitsu-api\lib\client\apps.js:85:5
cloud list
✓ should show the endpoints
♢ jitsu/commands/malformed
app list
✓ should exit gracefully
apps derploy
✓ should exit gracefully
env lost
✓ should exit gracefully
error: Sorry, socketio is not a node app
error: Error running command install socketio
install socketio
✓ should exit with an error
♢ jitsu/commands/databases
databases list
✓ should respond with no error
databases list
✓ should prompt for credentials
databases get test
✓ should respond with no error
databases get test
✓ should prompt for credentials
databases create couch test2
✓ should respond with no error
error: Database name is required
databases create
✓ should respond with no error
databases create couch test4
✓ should prompt for credentials
databases destroy test3
✓ should respond with no error
databases destroy test4
✓ should prompt for credentials
♢ jitsu/commands/env
env list
✓ should respond with no error
env list
✓ should prompt for credentials
env list foobar
✓ should respond with no error
env list barbaz
✓ should respond with no error
env get foo
✓ should respond with no error
env get foo
✓ should prompt for credentials
env get barbaz ping
✓ should respond with no error
error: Environment variable name and value and both required
error: Error running command env set
env set
✓ Should exit with an error
env set test truthy
✓ should respond with no error
env set test truthy
✓ should prompt for credentials
env set barbaz delete test
✓ should respond with no error
env set delete test
✓ should respond with no error
env delete delete
✓ should respond with no error
env delete delete
✓ should prompt for credentials
env delete barbaz delete
✓ should respond with no error
env clear
✓ The current app should have an empty env
env clear barbaz
✓ The specified app should have an empty env
env save
✗ The current app should save enviroment variables
TypeError: Object #<Object> has no method 'existsSync'
at Object.assertion (C:\jitsu\test\commands\env-test.js:342:28)
at runTest (C:\jitsu\node_modules\vows\lib\vows.js:132:26)
at EventEmitter.<anonymous> (C:\jitsu\node_modules\vows\lib\vows.js:78:9)
at EventEmitter.<anonymous> (events.js:88:20)
at EventEmitter.emit (C:\jitsu\node_modules\vows\lib\vows.js:237:24)
at C:\jitsu\node_modules\vows\lib\vows\context.js:32:52
at Object.callback (C:\jitsu\node_modules\vows\lib\vows\context.js:46:29)
at C:\jitsu\test\helpers\macros.js:55:23
at C:\jitsu\lib\jitsu.js:243:7
at C:\jitsu\lib\jitsu\commands\env.js:295:11
env save barbaz
✗ The specified app should save enviroment variables
TypeError: Object #<Object> has no method 'existsSync'
at Object.assertion (C:\jitsu\test\commands\env-test.js:362:28)
at runTest (C:\jitsu\node_modules\vows\lib\vows.js:132:26)
at EventEmitter.<anonymous> (C:\jitsu\node_modules\vows\lib\vows.js:78:9)
at EventEmitter.<anonymous> (events.js:88:20)
at EventEmitter.emit (C:\jitsu\node_modules\vows\lib\vows.js:237:24)
at C:\jitsu\node_modules\vows\lib\vows\context.js:32:52
at Object.callback (C:\jitsu\node_modules\vows\lib\vows\context.js:46:29)
at C:\jitsu\test\helpers\macros.js:55:23
at C:\jitsu\lib\jitsu.js:243:7
at C:\jitsu\lib\jitsu\commands\env.js:295:11
env save env_vars.json
✗ The current app should save enviroment variables to the specified filename
TypeError: Object #<Object> has no method 'existsSync'
at Object.assertion (C:\jitsu\test\commands\env-test.js:389:28)
at runTest (C:\jitsu\node_modules\vows\lib\vows.js:132:26)
at EventEmitter.<anonymous> (C:\jitsu\node_modules\vows\lib\vows.js:78:9)
at EventEmitter.<anonymous> (events.js:88:20)
at EventEmitter.emit (C:\jitsu\node_modules\vows\lib\vows.js:237:24)
at C:\jitsu\node_modules\vows\lib\vows\context.js:32:52
at Object.callback (C:\jitsu\node_modules\vows\lib\vows\context.js:46:29)
at C:\jitsu\test\helpers\macros.js:55:23
at C:\jitsu\lib\jitsu.js:243:7
at C:\jitsu\lib\jitsu\commands\env.js:295:11
env save barbaz env_vars.json
✗ The specified app should save enviroment variables to the specified filename
TypeError: Object #<Object> has no method 'existsSync'
at Object.assertion (C:\jitsu\test\commands\env-test.js:410:28)
at runTest (C:\jitsu\node_modules\vows\lib\vows.js:132:26)
at EventEmitter.<anonymous> (C:\jitsu\node_modules\vows\lib\vows.js:78:9)
at EventEmitter.<anonymous> (events.js:88:20)
at EventEmitter.emit (C:\jitsu\node_modules\vows\lib\vows.js:237:24)
at C:\jitsu\node_modules\vows\lib\vows\context.js:32:52
at Object.callback (C:\jitsu\node_modules\vows\lib\vows\context.js:46:29)
at C:\jitsu\test\helpers\macros.js:55:23
at C:\jitsu\lib\jitsu.js:243:7
at C:\jitsu\lib\jitsu\commands\env.js:295:11
env load
✓ The current app should load enviroment variables from env.json
env load barbaz
✓ The specified app should load enviroment variables from env.json
env load env_vars.json
✓ The current app should load enviroment variables from the specified file
env load barbaz env_vars.json
✓ The specified app should load enviroment variables from the specified file
Remove
✓ test envvar .json files
♢ jitsu/commands/logs
logs
✓ should respond with no error
logs
✓ should prompt for credentials
logs app
✓ should respond with no error
logs app
✓ should prompt for credentials
logs app application
✓ should respond with no error
logs app application
✓ should prompt for credentials
logs app application 10
✓ should respond with no error
♢ jitsu/commands/no-colors
when using the --no-colors flag
✓ output does not contain ansi codes
♢ jitsu/commands/package
package create
✓ should create the target tarball
♢ jitsu/commands/snapshots
snapshots list application
✓ should respond with no error
snapshots list application
✓ should prompt for credentials
snapshots list application2
✓ should respond with no error
snapshots activate application2
✓ should prompt for credentials
snapshots activate application2
✓ should respond with no error
snapshots activate application2
✓ should prompt for credentials
snapshots destroy application3
✓ should respond with no error
snapshots destroy application3
✓ should prompt for credentials
snapshots list
✓ should respond with no error
snapshots activate
✓ should respond with no error
snapshots destroy
✓ should respond with no error
♢ jitsu/commands/tokens
tokens list
✓ should respond with no error
tokens list adam
✓ should respond with no error
tokens create
✓ should respond with no error
tokens create test-token
✓ should respond with no error
tokens list
✓ should respond with no error
tokens destroy test-token
✓ should respond with no error
tokens create adam test-token
✓ should respond with no error
tokens list adam
✓ should respond with no error
tokens destroy adam test-token
✓ should respond with no error
♢ jitsu/commands/users
error: Error running command users confirm jimmy
error: Nodejitsu Error (400): Bad Request
users confirm jimmy
✓ should respond with a 400 error
users confirm elvis
✓ should respond with no error
♢ jitsu/lib/package
name starting with .
✓ should be invalid
name starting with _
✓ should be invalid
name containing -
✓ should be valid
name containing spaces
✓ should be invalid
name containing interior .
✓ should be valid
name containing %
✓ should be invalid
name containing @
✓ should be invalid
name containing :
✓ should be invalid
name containing +
✓ should be invalid
name containing /
✓ should be invalid
name node_modules
✓ should be invalid
name favicon.ico
✓ should be invalid
name containing unicode(๛ಠ_ಠ☠☃❤⁂⍨⋙‽)
✓ should be valid
subdomain starting with 9
✓ should be invalid
subdomain starting with _
✓ should be invalid
subdomain containing -
✓ should be valid
subdomain containing spaces
✓ should be invalid
subdomain containing .
✓ should be valid
subdomain containing %
✓ should be invalid
subdomain containing @
✓ should be invalid
subdomain containing :
✓ should be invalid
subdomain end with number
✓ should be valid
subdomain end with -
✓ should be invalid
subdomain containing unicode(๛ಠ_ಠ☠☃❤⁂⍨⋙‽)
✓ should be valid
✗ Errored » 109 honored ∙ 4 errored (21.774s)
npm ERR! Test failed. See above for more details.
npm ERR! not ok code undefined
npm ERR! not ok code 1
PS C:\jitsu>
Raw
node0.8.22.ps1
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.
PS C:\Users\fred rosak> cd c:/jitsu
PS C:\jitsu> node -v
v0.8.22
PS C:\jitsu> npm -v
1.2.14
PS C:\jitsu> npm test
> jitsu@0.12.8 test C:\jitsu
> vows test/commands/*-test.js test/lib/*-test.js --spec -i
♢ jitsu/commands/apps
apps list
✓ should respond with no error
apps list
✓ should prompt for credentials
apps view application2
✓ should respond with no error
apps view application2
✓ should prompt for credentials
apps start application3
✓ should respond with no error
apps start application3
✓ should prompt for credentials
apps stop application3
✓ should respond with no error
apps stop application3
✓ should prompt for credentials
apps view
✓ should respond with no error
apps start
✓ should respond with no error
apps stop
✓ should respond with no error
error: The subdomain requested is already in use
apps deploy
✓ should respond with no error
error: Error: Invalid package.json file
error: Please make sure C:\jitsu\test\fixtures\example-app\package.json is valid JSON
error: Error running command apps deploy
apps deploy
✓ should display an error on broken package.json
cloud example-app
✓ should show cloud info
cloud
✓ should show cloud info
cloud joyent
✓ should show cloud info
cloud example-app joyent
✓ should respond with no error
error: Error starting example-app
error: Error running command cloud example-app unknow-provider somedc
error: Unknown cloud: unknow-provider somedc
error: Error: Unknown cloud: unknow-provider somedc
error: at iterate (C:\jitsu\node_modules\nodejitsu-api\lib\client\client.js:114:21)
error: at loop (C:\jitsu\node_modules\nodejitsu-api\lib\client\helpers.js:63:7)
error: at Array.forEach (native)
cloud example-app unknow-provider somedc
✓ should fail
error: at Object.map (C:\jitsu\node_modules\nodejitsu-api\lib\client\helpers.js:62:9)
error: at completed (C:\jitsu\node_modules\nodejitsu-api\lib\client\client.js:103:11)
error: at Object.iterate (C:\jitsu\node_modules\nodejitsu-api\lib\client\helpers.js:35:27)
error: at Client.cloud (C:\jitsu\node_modules\nodejitsu-api\lib\client\client.js:99:9)
error: at executeCloud (C:\jitsu\node_modules\nodejitsu-api\lib\client\apps.js:237:10)
error: at Apps.datacenter.self.cloud.method (C:\jitsu\node_modules\nodejitsu-api\lib\client\apps.js:232:7)
error: at Apps.view (C:\jitsu\node_modules\nodejitsu-api\lib\client\apps.js:85:5)
cloud list
✓ should show the endpoints
♢ jitsu/commands/malformed
app list
✓ should exit gracefully
apps derploy
✓ should exit gracefully
env lost
✓ should exit gracefully
error: Sorry, socketio is not a node app
error: Error running command install socketio
install socketio
✓ should exit with an error
♢ jitsu/commands/databases
databases list
✓ should respond with no error
databases list
✓ should prompt for credentials
databases get test
✓ should respond with no error
databases get test
✓ should prompt for credentials
databases create couch test2
✓ should respond with no error
error: Database name is required
databases create
✓ should respond with no error
databases create couch test4
✓ should prompt for credentials
databases destroy test3
✓ should respond with no error
databases destroy test4
✓ should prompt for credentials
♢ jitsu/commands/env
env list
✓ should respond with no error
env list
✓ should prompt for credentials
env list foobar
✓ should respond with no error
env list barbaz
✓ should respond with no error
env get foo
✓ should respond with no error
env get foo
✓ should prompt for credentials
env get barbaz ping
✓ should respond with no error
error: Environment variable name and value and both required
error: Error running command env set
env set
✓ Should exit with an error
env set test truthy
✓ should respond with no error
env set test truthy
✓ should prompt for credentials
env set barbaz delete test
✓ should respond with no error
env set delete test
✓ should respond with no error
env delete delete
✓ should respond with no error
env delete delete
✓ should prompt for credentials
env delete barbaz delete
✓ should respond with no error
env clear
✓ The current app should have an empty env
env clear barbaz
✓ The specified app should have an empty env
env save
✓ The current app should save enviroment variables
env save barbaz
✓ The specified app should save enviroment variables
env save env_vars.json
✓ The current app should save enviroment variables to the specified filename
env save barbaz env_vars.json
✓ The specified app should save enviroment variables to the specified filename
env load
✓ The current app should load enviroment variables from env.json
env load barbaz
✓ The specified app should load enviroment variables from env.json
env load env_vars.json
✓ The current app should load enviroment variables from the specified file
env load barbaz env_vars.json
✓ The specified app should load enviroment variables from the specified file
Remove
✓ test envvar .json files
♢ jitsu/commands/logs
logs
✓ should respond with no error
logs
✓ should prompt for credentials
logs app
✓ should respond with no error
logs app
✓ should prompt for credentials
logs app application
✓ should respond with no error
logs app application
✓ should prompt for credentials
logs app application 10
✓ should respond with no error
♢ jitsu/commands/no-colors
when using the --no-colors flag
✓ output does not contain ansi codes
♢ jitsu/commands/package
package create
✓ should create the target tarball
♢ jitsu/commands/snapshots
snapshots list application
✓ should respond with no error
snapshots list application
✓ should prompt for credentials
snapshots list application2
✓ should respond with no error
snapshots activate application2
✓ should prompt for credentials
snapshots activate application2
✓ should respond with no error
snapshots activate application2
✓ should prompt for credentials
snapshots destroy application3
✓ should respond with no error
snapshots destroy application3
✓ should prompt for credentials
snapshots list
✓ should respond with no error
snapshots activate
✓ should respond with no error
snapshots destroy
✓ should respond with no error
♢ jitsu/commands/tokens
tokens list
✓ should respond with no error
tokens list adam
✓ should respond with no error
tokens create
✓ should respond with no error
tokens create test-token
✓ should respond with no error
tokens list
✓ should respond with no error
tokens destroy test-token
✓ should respond with no error
tokens create adam test-token
✓ should respond with no error
tokens list adam
✓ should respond with no error
tokens destroy adam test-token
✓ should respond with no error
♢ jitsu/commands/users
error: Error running command users confirm jimmy
error: Nodejitsu Error (400): Bad Request
users confirm jimmy
✓ should respond with a 400 error
users confirm elvis
✓ should respond with no error
♢ jitsu/lib/package
name starting with .
✓ should be invalid
name starting with _
✓ should be invalid
name containing -
✓ should be valid
name containing spaces
✓ should be invalid
name containing interior .
✓ should be valid
name containing %
✓ should be invalid
name containing @
✓ should be invalid
name containing :
✓ should be invalid
name containing +
✓ should be invalid
name containing /
✓ should be invalid
name node_modules
✓ should be invalid
name favicon.ico
✓ should be invalid
name containing unicode(๛ಠ_ಠ☠☃❤⁂⍨⋙‽)
✓ should be valid
subdomain starting with 9
✓ should be invalid
subdomain starting with _
✓ should be invalid
subdomain containing -
✓ should be valid
subdomain containing spaces
✓ should be invalid
subdomain containing .
✓ should be valid
subdomain containing %
✓ should be invalid
subdomain containing @
✓ should be invalid
subdomain containing :
✓ should be invalid
subdomain end with number
✓ should be valid
subdomain end with -
✓ should be invalid
subdomain containing unicode(๛ಠ_ಠ☠☃❤⁂⍨⋙‽)
✓ should be valid
✓ OK » 113 honored (18.355s)
PS C:\jitsu>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment