xervoio / cli Goto Github PK

My Node is built nativley on Ubuntu 14:04 all other npm modules installed globally work fine apart from modulus.

steps (after updating node, npm etc) - done as sudo

$ npm install -g modulus

``$ modulus login
modulus: command not found
`

Checked paths, modules, install etc no problem I can run node and other modules as I said..

If there is a failure when building a project during deploy I've noticed what seems to be a new feature, or at least log output:

Build failed, reverting project.

The problem is I don't think this is printed to stderr, so in my case at least a CI build within which the deploy is running doesn't know that the deploy actually failed (on some level). So unless someone reviews the log output carefully the build otherwise appears to have been successful.

Using modulus CLI 3.01 on OS X 10.9. The app is on Meteor 0.9.4

The error is:

Error: Can't find npm module 'bcrypt'. Did you forget to call 'Npm.depends' in package.js within the 'npm-bcrypt' package?
    at Object.Npm.require (/mnt/data/1/programs/server/boot.js:113:17)
    at Package (packages/npm-bcrypt/wrapper.js:1)
    at /mnt/data/1/programs/server/packages/npm-bcrypt.js:21:4
    at /mnt/data/1/programs/server/packages/npm-bcrypt.js:30:3
    at /mnt/data/1/programs/server/boot.js:168:10
    at Array.forEach (native)
    at Function._.each._.forEach (/mnt/data/1/node_modules/underscore/underscore.js:79:11)
    at /mnt/data/1/programs/server/boot.js:82:5
[2014-10-30T22:54:44.877Z] Failed to start application.

I've re-deployed a few times to no avail. Help!

Doesn't work atm.

Not sure which part of the stack this is.

Meteor project detected...

WARNING: The output directory is under your source tree.

Errors prevented bundling:
While linking the program:
error: bitpay is not compatible with architecture 'os.linux.x86_64'

undefined
[Error] Error: Conversion failed.

I'm trying to deploy my project but it's just stuck on Deploying Project...

When prompted for an option, code should catch invalid answers. It does not.

Example :

modulus project start
Welcome to Modulus
You are logged in as #####@########.com
Please choose which project to use:
  1) cool-project
  2) cooler-project
[?] project 9

/usr/local/lib/node_modules/modulus/lib/commands/project.js:548
odulus.io.print(util.format(foundPrint, projects[result.project - 1].name.data
                                                                    ^
TypeError: Cannot read property 'name' of undefined
    at /usr/local/lib/node_modules/modulus/lib/commands/project.js:548:76
    at /usr/local/lib/node_modules/modulus/node_modules/prompt/lib/prompt.js:316:32
    at /usr/local/lib/node_modules/modulus/node_modules/prompt/node_modules/utile/node_modules/async/lib/async.js:139:25
    at assembler (/usr/local/lib/node_modules/modulus/node_modules/prompt/lib/prompt.js:313:9)
    at /usr/local/lib/node_modules/modulus/node_modules/prompt/lib/prompt.js:322:32
    at /usr/local/lib/node_modules/modulus/node_modules/prompt/lib/prompt.js:597:5
    at Interface.onLine (/usr/local/lib/node_modules/modulus/node_modules/prompt/node_modules/read/lib/read.js:111:5)
    at Interface.EventEmitter.emit (events.js:95:17)
    at Interface._onLine (readline.js:202:10)
    at Interface._line (readline.js:531:8)

The modulus.io.prompt.get is not properly detecting that the provided answer is greater than the maximum defined in the schema.

in 4.0 I get: error: unknown option --force-npm-install'

Correct credentials for logging in not working with proxy.

Deploying a Meteor 0.9 projects gives:

Error: EACCES, permission denied error

This is related to this Demeteorizer bug, which has a patch (that does not work for the Demeteorizer shipped with Modulus) here.

Thanks for looking into this, I use your service for some Meteor apps.

I am getting this warning when deploying my app (deployment works fine though).

Bundling Meteor App...
This command has been deprecated in favor of 'meteor build', which allows you
to build for multiple platforms and outputs a directory instead of a single
tarball. See 'meteor help build'for more information.

To be honest I don't know what's happening. Everything works fine locally, and everything works fine when deploying with Meteor (0.8.3).

But when deploying (0.9.3.1) with modulus-cli or demeteorizer this happens on the browser and the page doesn't load.

Exception in defer callback: ReferenceError: Spacebars is not defined
    at null._render (http://xxxx.onmodulus.net/9aa21788febe55e7cc242ecbaedaeee44deb4504.js:12:16455)
    at null.<anonymous> (http://xxxx.onmodulus.net/9aa21788febe55e7cc242ecbaedaeee44deb4504.js:10:10005)
    at http://xxxx.onmodulus.net/9aa21788febe55e7cc242ecbaedaeee44deb4504.js:10:9113
    at Object.e._withCurrentView (http://xxxx.onmodulus.net/9aa21788febe55e7cc242ecbaedaeee44deb4504.js:10:12132)
    at http://xxxx.onmodulus.net/9aa21788febe55e7cc242ecbaedaeee44deb4504.js:10:9071
    at e.Computation._compute (http://xxxx.onmodulus.net/9aa21788febe55e7cc242ecbaedaeee44deb4504.js:2:13250)
    at new e.Computation (http://xxxx.onmodulus.net/9aa21788febe55e7cc242ecbaedaeee44deb4504.js:2:12513)
    at Object.e.autorun (http://xxxx.onmodulus.net/9aa21788febe55e7cc242ecbaedaeee44deb4504.js:2:14486)
    at e.View.autorun (http://xxxx.onmodulus.net/9aa21788febe55e7cc242ecbaedaeee44deb4504.js:10:9042)
    at http://xxxx.onmodulus.net/9aa21788febe55e7cc242ecbaedaeee44deb4504.js:10:9944 

No output on server side.

beeman@SN-BEEMAN:~/Projects/brendanhill-resume$ modulus login

node.js:201
throw e; // process.nextTick error, or 'error' event on first tick
^
TypeError: Object # has no method 'existsSync'
at new (/usr/local/lib/node_modules/modulus/lib/common/userConfig.js:5:10)
at Object. (/usr/local/lib/node_modules/modulus/lib/common/api.js:6:16)
at Module._compile (module.js:441:26)
at Object..js (module.js:459:10)
at Module.load (module.js:348:31)
at Function._load (module.js:308:12)
at Module.require (module.js:354:17)
at require (module.js:370:17)
at Object. (/usr/local/lib/node_modules/modulus/lib/modulus.js:2:18)
at Module._compile (module.js:441:26)
beeman@SN-BEEMAN:/Projects/brendanhill-resume$ node -v
v0.6.17
beeman@SN-BEEMAN:/Projects/brendanhill-resume$ npm -v
1.1.70

The simplicity of the scaling options UI is great, but currently there isn't an easy way to see which servos are running in which environments. We've noticed some variation in performance characteristics across servos but currently it's difficult to correlate that to an underlying region or provider. We suspect that's a likely culprit whether due to the traffic being routed (especially US vs. EU) or possible differences in the underlying infrastructure.

It'd be great if I could see a list of servos for each of my projects that included the values from process.env.MODULUS_IAAS and process.env.MODULUS_REGION. Adding this context in other places, such as when running modulus project logs would also be valuable.

I can't update modulus to 1.2.0. Update your shasum and test on what we're all using, 10.9.4 Macs with node & npm installed from brew.

npm update -g modulus
info trying registry request attempt 1 at 16:23:25
http GET https://registry.npmjs.org/modulus
http 304 https://registry.npmjs.org/modulus
npm ERR! Error: shasum check failed for /var/folders/6y/tndxp8r560v5gbbyn_sf0xz00000gn/T/npm-42680-TrCKMaUO/registry.npmjs.org/modulus/-/modulus-1.2.0.tgz
npm ERR! Expected: d80817db6881cdc67649c4a09d293d76fbed3f6d
npm ERR! Actual:   629350420e99e2f78830c0d178b4bc0be28bd773
npm ERR! From:     https://registry.npmjs.org/modulus/-/modulus-1.2.0.tgz
npm ERR!     at /usr/local/lib/node_modules/npm/node_modules/sha/index.js:38:8
npm ERR!     at ReadStream.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/sha/index.js:85:7)
npm ERR!     at ReadStream.emit (events.js:117:20)
npm ERR!     at _stream_readable.js:943:16
npm ERR!     at process._tickCallback (node.js:419:13)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

Any recommendations here?

[me@Taco ~/Projects/myapp]$ meteor --version
loading observatory: apollo
loading observatory: galileo
Meteor 0.9.2.2
[me@Taco ~/Projects/myapp]$ modulus --version
1.2.2
[me@Taco ~/Projects/myapp]$ modulus deploy
Welcome to Modulus
You are logged in as [email protected]
[?] Are you sure you want to use project myapp? (yes) 
Meteor project detected...
Determining Meteor version...
Meteor version: observatory:
Bundling Meteor App...

/usr/local/lib/node_modules/modulus/node_modules/demeteorizer/node_modules/semver/semver.js:273
    throw new TypeError('Invalid Version: ' + version);
          ^
TypeError: Invalid Version: observatory:.undefined.0
    at new SemVer (/usr/local/lib/node_modules/modulus/node_modules/demeteorizer/node_modules/semver/semver.js:273:11)
    at compare (/usr/local/lib/node_modules/modulus/node_modules/demeteorizer/node_modules/semver/semver.js:460:10)
    at Function.lte (/usr/local/lib/node_modules/modulus/node_modules/demeteorizer/node_modules/semver/semver.js:514:10)
    at Demeteorizer.getBundleCommand (/usr/local/lib/node_modules/modulus/node_modules/demeteorizer/lib/demeteorizer.js:151:13)
    at Demeteorizer.bundle (/usr/local/lib/node_modules/modulus/node_modules/demeteorizer/lib/demeteorizer.js:176:18)
    at /usr/local/lib/node_modules/modulus/node_modules/demeteorizer/lib/demeteorizer.js:54:12
    at /usr/local/lib/node_modules/modulus/node_modules/demeteorizer/node_modules/async/lib/async.js:551:21
    at /usr/local/lib/node_modules/modulus/node_modules/demeteorizer/node_modules/async/lib/async.js:227:13

The screenshot is pretty self explanatory and this problem is very rare in most CLI apps.

This is my log on installing.

C:\nodejs_curso>npm install -g modulus
npm http GET https://registry.npmjs.org/modulus
npm http 304 https://registry.npmjs.org/modulus
npm http GET https://registry.npmjs.org/colors
npm http GET https://registry.npmjs.org/pkginfo
npm http GET https://registry.npmjs.org/prompt
npm http GET https://registry.npmjs.org/walkr
npm http GET https://registry.npmjs.org/zipstream
npm http GET https://registry.npmjs.org/async
npm http GET https://registry.npmjs.org/request/2.12.0
npm http GET https://registry.npmjs.org/progress
npm http GET https://registry.npmjs.org/node-uuid/1.3.3
npm http GET https://registry.npmjs.org/commander-plus
npm http GET https://registry.npmjs.org/underscore
npm http 304 https://registry.npmjs.org/walkr
npm http 304 https://registry.npmjs.org/pkginfo
npm http 304 https://registry.npmjs.org/colors
npm http 304 https://registry.npmjs.org/zipstream
npm http 304 https://registry.npmjs.org/prompt
npm http 304 https://registry.npmjs.org/async
npm http 304 https://registry.npmjs.org/request/2.12.0
npm http 304 https://registry.npmjs.org/progress
npm http 304 https://registry.npmjs.org/node-uuid/1.3.3
npm http 304 https://registry.npmjs.org/commander-plus
npm http 304 https://registry.npmjs.org/underscore
npm ERR! git clone git://github.com/onmodulus/chunk-loader.git CreateProcessW: E
l sistema no puede encontrar el archivo especificado.
npm ERR! Error: git "clone" "git://github.com/onmodulus/chunk-loader.git" "C:\\ Users\\aramos\\AppData\\Local\\Temp\\npm-4972\\1358967818091-0.09462746675126255 " failed with 127
npm ERR! at ChildProcess. (C:\Program Files\nodejs\node_modules\n
pm\lib\utils\exec.js:56:20)
npm ERR! at ChildProcess.EventEmitter.emit (events.js:99:17)
npm ERR! at Process._handle.onexit (child_process.js:678:10)
npm ERR! If you need help, you may report this log at:
npm ERR! http://github.com/isaacs/npm/issues
npm ERR! or email it to:
npm ERR! [email protected]

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nod
ejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "modulus"
npm ERR! cwd C:\nodejs_curso
npm ERR! node -v v0.8.17
npm ERR! npm -v 1.2.0
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! C:\nodejs_curso\npm-debug.log
npm ERR! not ok code 0

I have a meteor app.
When I do modulus deploy, I get error:

TypeError: Cannot read property 'concat' of undefined
at /Users/trent/.nvm/versions/node/v0.12.2/lib/node_modules/modulus/lib/common/verifyPackage.js:74:25
at /Users/trent/.nvm/versions/node/v0.12.2/lib/node_modules/modulus/node_modules/async/lib/async.js:190:13
at /Users/trent/.nvm/versions/node/v0.12.2/lib/node_modules/modulus/node_modules/async/lib/async.js:116:25
at /Users/trent/.nvm/versions/node/v0.12.2/lib/node_modules/modulus/node_modules/async/lib/async.js:187:17
at /Users/trent/.nvm/versions/node/v0.12.2/lib/node_modules/modulus/node_modules/async/lib/async.js:491:34
at checkStartScript (/Users/trent/.nvm/versions/node/v0.12.2/lib/node_modules/modulus/lib/common/verifyPackage.js:11:52)
at /Users/trent/.nvm/versions/node/v0.12.2/lib/node_modules/modulus/lib/common/verifyPackage.js:70:7
at /Users/trent/.nvm/versions/node/v0.12.2/lib/node_modules/modulus/node_modules/async/lib/async.js:486:21
at /Users/trent/.nvm/versions/node/v0.12.2/lib/node_modules/modulus/node_modules/async/lib/async.js:185:13
at iterate (/Users/trent/.nvm/versions/node/v0.12.2/lib/node_modules/modulus/node_modules/async/lib/async.js:108:13)

I would very much like to be able to update my environment settings from my build server using the modulus cli. TOKENS seems only supported in the deploy action.

What I would like to do is something like this.

export MODULUS_TOKEN=xxx
modulus env set "tada" "todo"

without the modulus cli asking me about the project name and just rely on the token set.

Causing error Directory "/Users/jperl/myapp/false" does not exist.

Sorry, guys, but it seems that every time I try to deploy my App, something goes wrong. This one I have no idea what can it be.

Modulus-cli output error (one of them):

npm ERR! System Linux 3.2.0-41-virtual
npm ERR! command "/mnt/nave/installed/0.10.33/bin/node" "/mnt/nave/installed/0.10.33/bin/npm" "install" "--production" "--registry" "http://registry.npmjs.org" "--cache" "/mnt/data/.npm"
npm ERR! cwd /mnt/data/1
npm ERR! node -v v0.10.33
npm ERR! npm -v 1.4.28
npm ERR! path /mnt/data/1/node_modules/css-parse/test
npm ERR! fstream_path /mnt/data/1/node_modules/css-parse/test
npm ERR! fstream_type Directory
npm ERR! fstream_class DirWriter
npm ERR! code ENOSPC
npm ERR! errno 54
npm ERR! fstream_stack /nave/installed/0.10.33/lib/node_modules/npm/node_modules/fstream/lib/dir-writer.js:36:23
npm ERR! fstream_stack /nave/installed/0.10.33/lib/node_modules/npm/node_modules/mkdirp/index.js:46:53
npm ERR! fstream_stack Object.oncomplete (fs.js:107:15)
npm ERR! nospc ENOSPC, write
npm ERR! nospc This is most likely not a problem with npm itself
npm ERR! nospc and is related to insufficient space on your system.

Application error:

Error: `/mnt/data/1/node_modules/fibers/bin/linux-x64-v8-3.14/fibers.node` is missing. Try reinstalling `node-fibers`?
    at Object.<anonymous> (/mnt/data/1/node_modules/fibers/fibers.js:13:8)
    at Module._compile (module.js:456:26)

Any idea ?

How can I automate my use of modulus cli if it keeps asking me "yes" every time I run it?

Hi, one of the very few irritations I've been having with the command line tool is that you have to select a project every time you deploy (please correct me if I'm wrong).

Would it be possible to allow a .modulus file or something inside a directory which specifies the project to deploy to? That way I can just run modulus deploy without having to remember to wait and select a project.

It will probably also avoid potential mistakes – what if I accidentally select the wrong project?

Thanks,
Rowan

I just downloaded the latest modulus code from Github, and when I ran
"modulus login", I get an error that:

TypeError: Cannot read property 'api_uri' of undefined

Here's full stack returned:

$ modulus login

/usr/lib/node_modules/modulus/lib/common/api.js:8
if (typeof userConfig.data.api_uri !== 'undefined') {
                          ^
TypeError: Cannot read property 'api_uri' of undefined
    at Object.<anonymous> (/usr/lib/node_modules/modulus/lib/common/api.js:8:27)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:312:12)
    at Module.require (module.js:364:17)
    at require (module.js:380:17)
    at Object.<anonymous> (/usr/lib/node_modules/modulus/lib/modulus.js:2:18)
    at Module._compile (module.js:456:26)
    at Object.Module._extensions..js (module.js:474:10)

It's not clear what I'm supposed to do from here to continue logging in.

I'm upgraded a Meteor app to 1.0.2.1 and upgraded all its packages. There's a ShareJS package using the Ace editor. Everything works correctly locally.

I run '''.demeteorizer''', cd into the .demeteorized directory, then run '''modulus deploy'''. The build and deploy is successful, but the browser receives a 500 error when trying to retrieve this file:
'''packages/mizzao_sharejs/.npm/package/node_modules/share/webclient/ace.js'''

Here's the broken production website:
https://www.seemecode.com/

Here's the server log:
'''{"line":"457","file":"webapp_server.js","message":"Error serving static file Error: ENOENT, stat '/mnt/data/2/programs/web.browser/packages/mizzao_sharejs/.npm/package/node_modules/share/webclient/ace.js'","time":{"$date":1419661767968},"level":"error"}'''

Any ideas why this works locally, but not after running '''.demeteorizer''' and '''modulus deploy'''? Thanks!

Code is not being deployed minified using either -D or --meteor-debug

Thanks for updating demeteorizer to work with Meteor 0.9.x ! But it seems there is a side effect, projects which have not yet upgraded to the new version of Meteor can no longer deploy with the modulus CLI 'deploy' command. At least I am unable to get it to work with my project.

For those still using earlier versions of Meteor, 0.8.3 or lower who are having issues like I am, theres an easy fix. Just specify the last compatible version of the modulus CLI when installing from NPM like so:
npm install -g [email protected]

I have a project I deployed to modulus using 'modulus deploy'. Later I had to changes to be made to just a file and that made me miserable because I used the same command and it overwrote the existing files and all the uploaded files that do not exist on the local server were gone. How can I make changes to the server without touching any other files?

I am trying to deploy my meteor app on Modulus but I am getting these errors on the console

Error: Can't find npm module 'meteor-deque'. Did you forget to call 'Npm.depends' in package.js within the 'meteor' package?
at Object.Npm.require (/mnt/app/bundle/programs/server/boot.js:175:17)
at Meteor.startup (packages/meteor/fiber_helpers.js:17:1)
at /mnt/app/bundle/programs/server/packages/meteor.js:816:4
at /mnt/app/bundle/programs/server/packages/meteor.js:1274:3
at /mnt/app/bundle/programs/server/boot.js:242:10
at Array.forEach (native)
at Function._.each._.forEach (/mnt/app/bundle/programs/server/node_modules/underscore/underscore.js:79:11)
at /mnt/app/bundle/programs/server/boot.js:137:5

npm ERR! Linux 3.13.0-46-generic
npm ERR! argv "node" "/mnt/app/.modulus/nvm/v0.10.40/bin/npm" "start"
npm ERR! node v0.10.40
npm ERR! npm  v3.3.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: `node ../../main`
npm ERR! Exit status 8
npm ERR! 
npm ERR! Failed at the [email protected] start script 'node ../../main'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the meteor-dev-bundle package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node ../../main
npm ERR! You can get their info via:
npm ERR!     npm owner ls meteor-dev-bundle
npm ERR! There is likely additional logging output above.

My node version is 0.12.7
My meteor version is 1.2.1

Just dropping a note that the newest version of demeteorizer fixes an issue for me in modulus-cli, and it would be great to update modulus-cli to use the latest version of demeteorizer.

Trying to deploy my Meteor app and I'm getting the following error

Meteor project detected...
Input: /Users/macbookpro/Platfarm/R&D/App/platfarm-app
Output: /Users/macbookpro/Platfarm/R&D/App/platfarm-app/.demeteorized
Determining Meteor version...
Meteor version: 1.0.1
Bundling Meteor App...
undefined
[Error] Error: Command failed: /bin/sh: line 0: cd: /Users/macbookpro/Platfarm/R: No such file or directory
/bin/sh: D/App/platfarm-app/.demeteorized: No such file or directory
/bin/sh: D/App/platfarm-app: No such file or directory

In the documentation for the Log fetching feature, the output confusingly shows an app launching before the logs are delivered. That deserves some further explanation.

Is that app output supposed to be /my/ app. Then why if is it being started up if it's already running? If it wasn't already running, there wouldn't be much point in fetching the logs for it just after starting it since they would be mostly empty.

Or is the app output shown /your/ app... Perhaps the log fetcher is itself implemented as Modulus app which has to be started? If that's the case, how you implement your log fetcher is none of my concern. Simply output some sort of generic progress bar would do, eventually resulting in "Logs successfully retrieved".

Until the docs are updated to clarify what's going on, I'm unlikely to try the log fetching feature on a production site until it's clearer why it's starting up a Modulus app just to fetch logs.

$ modulus project logs -p "Lizard Locator"
Welcome to Modulus
You are logged in as spiderman
INFO: Attaching persistent storage.
INFO: Found package.json file: /package.json
INFO: Node version not specified in package.json, using latest stable version.
INFO: Initializing Node v0.10.13
INFO: Running npm install.
INFO: Registry: http://registry.npmjs.org
npm http GET http://registry.npmjs.org/express
npm http 304 http://registry.npmjs.org/express
npm http GET http://registry.npmjs.org/qs
npm http GET http://registry.npmjs.org/connect
npm http GET http://registry.npmjs.org/mime/1.2.4
npm http GET http://registry.npmjs.org/mkdirp/0.3.0
npm http 304 http://registry.npmjs.org/qs
npm http 304 http://registry.npmjs.org/connect
npm http 304 http://registry.npmjs.org/mime/1.2.4
npm http 304 http://registry.npmjs.org/mkdirp/0.3.0
npm http GET http://registry.npmjs.org/mime/-/mime-1.2.4.tgz
npm http GET http://registry.npmjs.org/mkdirp/-/mkdirp-0.3.0.tgz
npm http GET http://registry.npmjs.org/qs/-/qs-0.4.2.tgz
npm http 200 http://registry.npmjs.org/mime/-/mime-1.2.4.tgz
npm http 200 http://registry.npmjs.org/mkdirp/-/mkdirp-0.3.0.tgz
npm http 200 http://registry.npmjs.org/qs/-/qs-0.4.2.tgz
npm http GET http://registry.npmjs.org/formidable
npm http 304 http://registry.npmjs.org/formidable
[email protected] node_modules/express
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected] ([email protected])
INFO: Main file found: /app.js
INFO: Starting application.
Express server started on port 8080
[2013-08-22T17:53:42.245Z] Application initialized with pid 11010

[✓] Logs successfully retrieved.

When I run modulus deploy I'm getting the following messages, but my app is using meteor 1.0.1

Meteor project detected...
Input: /Users/macbookpro/Almog_Design/My_Projects/Linkly/linklyapp
Output: /Users/macbookpro/Almog_Design/My_Projects/Linkly/linklyapp/.demeteorized
Determining Meteor version...
Meteor version: 0.9.4
Bundling Meteor App...
WARNING: 'bundle' has been deprecated. Use 'build' instead.
meteor bundle generation complete.
Finding dependencies...
139 dependencies found.
Creating package.json file.
package.json file generation complete.
Deleting node_modules folders.
Compressing project...
4.0 MB written
Uploading project...
Upload progress [===================] 100%
Deploying Project...

When I deploy and try to select a node version this happens:

$ modulus deploy -n 0.10.36 -p project
Welcome to Modulus
You are logged in as ernestorocha
Selecting project

And later on the output:

INFO: Found package.json file: /package.json
INFO: Node version specified in package.json: 0.10.33
INFO: Initializing Node v0.10.33

Any idea ?

I've just created a new project, but not deployed anything yet, so my project has a status of "NONE", I then tried to issue modulus project scale 2 and selected my project, as I know I'll need 2 servos for it.

Scaling shows as successful in the web UI, but in the command prompt, it just had the indeterminate progress bar going continuously. I suspect that's because you're checking the project status goes to "running" (https://github.com/onmodulus/modulus-cli/blob/master/lib/controllers/project.js#L526)

While deploying meteor app modulus deploy gives error Unable to determine Node version and fail deploy.

Everything was OK couple of days ago when I deployed same app with same code.

OS : Windows 8.1
Meteor version : 1.2.0.4
Node version : 5.0.0

Compressing project...
23.3 MB written
Uploading project...
Upload progress [===================] 100%
Deploying project into Node.js runtime...
Starting build.
Creating directories for build environment.
Downloading source.
Executing build.
Package found: /E/Website/Meteor/meteor 5/webstorm_cik/.demeteorized/bundle/programs/server/package.json
Unable to determine Node version. Verify package.json has no errors.
Build attempt failed, attempting again.

Meteor 0.8.1 appears to have different options for the bundle command.

on os x, the modulus cli command will have syntax error if my path have unusual characters in them (/Users/Dropbox\ (Personal)/something)

I think it's either the space, the \ from the space or the ( that is causing the problem. posting on mobile now, will provide the actual error message when I am back on laptop

I think it would be useful if modulus would add any node module that exists in the bundledDependencies to the zip archive. A lot of my use case is working with a project that has a number of private repositories that i want bundled with my application but not necessarily all the standard node_modules like express/request....

This wouldn't be a big issue except that modulus does not follow symbolic links to folders in node_modules when the -m flag is specified. Making any 'npm link' commands people do not get zipped in the archive.

I couldn't find a way to delete a project, this should be possible.

After updating to modulus 3.7.1 I get a TypeError when running modulus project commands. Login appears to work fine.

/usr/local/lib/node_modules/modulus/lib/commands/project.js:993
        projects[i].images.run ?
                          ^
TypeError: Cannot read property 'run' of undefined
    at Object.project.chooseProjectPrompt (/usr/local/lib/node_modules/modulus/lib/commands/project.js:993:27)
    at /usr/local/lib/node_modules/modulus/lib/commands/project.js:669:15
    at IncomingMessage.<anonymous> (/usr/local/lib/node_modules/modulus/lib/librarian/http.js:134:9)
    at IncomingMessage.EventEmitter.emit (events.js:117:20)
    at _stream_readable.js:919:16
    at process._tickCallback (node.js:419:13)

At least with the preview..

➜  device git:(menu) modulus deploy
Welcome to Modulus
You are logged in as [email protected]
Please choose which project to use:
  1) Dev Device
  2) Plus More Admin
  3) Plus More Device
  4) Plus More Hotel
  5) QA Device
[?] project 1
Selecting Dev Device

Meteor project detected...
Determining Meteor version...
Meteor version: 0.9.4-pre.6

Bundling Meteor App...
WARNING: 'bundle' has been deprecated. Use 'build' instead.

Supply the server hostname and port in the --server option
for mobile app builds.

[Error] Supply the server hostname and port in the --server option
for mobile app builds.

I've used the modulus deploy tool before without any issues. I updated the tool to the latest version this evening and now when I try to deploy, I get this output:

chase@blackbox:~/WebstormProjects/pointbox$ modulus deploy
Welcome to Modulus
You are logged in as chagwood
[?] Are you sure you want to use project pointbox? (yes)
Meteor project detected...
Input: /home/chase/WebstormProjects/pointbox
Output: /home/chase/WebstormProjects/pointbox/.demeteorized
Determining Meteor version...
Meteor version: 1.0
Bundling Meteor App...
undefined
[Error] Error: Command failed: This command has been deprecated in favor of 'meteor build', which allows you to
build for multiple platforms and outputs a directory instead of a single
tarball. See 'meteor help build' for more information.

Errors prevented bundling:
While Building the application:
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/node_modules/underscore.string/test/speed.js:62:9: Unexpected token let
node_modules/modulus/node_modules/request/node_modules/form-data/node_modules/combined-stream/node_modules/delayed-stream/test/run.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/examples/arguments.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/examples/choice.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/examples/constants.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/examples/help.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/examples/nargs.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/examples/parents.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/examples/prefix_chars.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/examples/sub_commands.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/examples/sum.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/esprima/bin/esparse.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/esprima/bin/esvalidate.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/request/node_modules/combined-stream/node_modules/delayed-stream/test/run.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/fstream-ignore/node_modules/fstream/node_modules/mkdirp/bin/cmd.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/fstream-ignore/node_modules/minimatch/node_modules/lru-cache/test/memory-leak.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/prompt/node_modules/utile/node_modules/mkdirp/bin/cmd.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/bin/js-yaml.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/mkdirp/bin/cmd.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/request/node_modules/bl/test/sauce.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/fstream-ignore/node_modules/fstream/node_modules/rimraf/bin.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/prompt/node_modules/utile/node_modules/rimraf/bin.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/update-notifier/node_modules/chalk/node_modules/strip-ansi/cli.js:1:15: Unexpected token ILLEGAL
node_modules/modulus/node_modules/demeteorizer/node_modules/semver/foot.js:8:1: Unexpected token }
node_modules/modulus/node_modules/demeteorizer/node_modules/semver/head.js:4:3: Unexpected end of input
node_modules/modulus/node_modules/update-notifier/node_modules/semver/foot.js:8:1: Unexpected token }
node_modules/modulus/node_modules/update-notifier/node_modules/semver/head.js:4:3: Unexpected end of input
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/node_modules/underscore.string/test/test_underscore/index.html:1: Can't set DOCTYPE here. (Meteor sets for you)
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/node_modules/underscore.string/test/test.html:1: Can't set DOCTYPE here. (Meteor sets for you)
node_modules/modulus/node_modules/update-notifier/node_modules/configstore/node_modules/js-yaml/node_modules/argparse/node_modules/underscore.string/test/test_standalone.html:1: Can't set DOCTYPE here. (Meteor sets for you)
node_modules/modulus/node_modules/prompt/node_modules/winston/node_modules/pkginfo/docs/pkginfo.html:1: Can't set DOCTYPE here. (Meteor sets for you)
node_modules/modulus/node_modules/update-notifier/node_modules/request/node_modules/node-uuid/test/test.html:1: bad formatting in HTML template
node_modules/modulus/node_modules/request/node_modules/node-uuid/test/test.html:1: bad formatting in HTML template
node_modules/modulus/node_modules/node-uuid/test/test.html:1: bad formatting in HTML template
node_modules/modulus/node_modules/pkginfo/docs/pkginfo.html:1: Can't set DOCTYPE here. (Meteor sets for you)
node_modules/modulus/node_modules/prompt/docs/prompt.html:1: Can't set DOCTYPE here. (Meteor sets for you)
node_modules/modulus/node_modules/colors/example.html:1: Can't set DOCTYPE here. (Meteor sets for you)
node_modules/modulus/node_modules/underscore/index.html:1: Can't set DOCTYPE here. (Meteor sets for you)

When I type modulus deploy, all I get is:

Welcome to Modulus
You are logged in as [email protected]

And then it just stays there. Are you guys down?

It's odd to constantly select the project for some command like modulus env it should be possible to have something like .modulus and set the desired project there so that the targeted project is inferred based on the presence of that file.

Eg. $ modulus env list -p api
Just like env set