autogenerated app error

[tiberule]

nodejs 0.6.19
after installation i did simple test
$ matador init tt1
$ cd !$ && npm install matador
$ cd all && node server.js

got bunch of errors

matador running on port 3000
soynode: Compile error
execvp(): No such file or directory

/srv/www/tt1/node_modules/matador/src/matador.js:431
throw err
^
Error: Error compiling templates
at ChildProcess. (/srv/www/tt1/node_modules/matador/node_modules/soynode/lib/soynode.js:177:18)
at ChildProcess.emit (events.js:70:17)
at maybeExit (child_process.js:362:16)
at Socket. (child_process.js:467:7)
at Socket.emit (events.js:67:17)
at Array.0 (net.js:335:10)
at EventEmitter._tickCallback (node.js:190:38)

[davidbyttow]

Seems to work for me with latest (1.1.5-beta):

$ matador init tt1
installing Matador into tt1
Success!
$ cd tt1
$ npm install matador

matador@1.1.5-beta ./node_modules/matador
├── colors@0.6.0-1
├── klass@1.2.2
├── valentine@1.5.5
├── uglify-js@1.3.2
├── hogan.js@2.0.0
├── optimist@0.3.4 (wordwrap@0.0.2)
├── connect@2.3.3 (bytes@0.0.1, fresh@0.0.1, range-parser@0.0.1, cookie@0.0.3, crc@0.2.0, debug@0.7.0, qs@0.4.2, mime@1.2.4, formidable@1.0.11)
└── soynode@0.1.4
$ node server.js
matador running on port 3000

then was able to render both localhost:3000 and localhost:3000/soy

[dpup]

Thanks for the report. It'd be nice if this worked out of the box without having to do any configuration, so we'll look into it.

[davidbyttow]

Note, I fixed this yesterday (or at least I thought it did). :-)

[dpup]

Heh, we replied at the same time. From the log it looks like the error is being thrown within the spawn command. Can't tell which directory doesn't exist. Probably inputDir.

[davidbyttow]

From the steps above, I don't understand "cd all && node server.js". You want to run the server.js in the generated directory, right?

[tiberule]

I did the same tests again.

$ node -v
v0.6.19

to be sure there will be fresh version
$ npm remove matador -g

$npm install -g matador
/usr/local/bin/matador -> /usr/local/lib/node_modules/matador/bin/matador.js
matador@1.1.5-beta /usr/local/lib/node_modules/matador
+-- colors@0.6.0-1
+-- klass@1.2.2
+-- valentine@1.5.5
+-- uglify-js@1.3.2
+-- hogan.js@2.0.0
+-- optimist@0.3.4 (wordwrap@0.0.2)
+-- soynode@0.1.4
L-- connect@2.3.3 (bytes@0.0.1, range-parser@0.0.1, fresh@0.0.1, cookie@0.0.3, crc@0.2.0, debug@0.7.0, qs@0.4.2, mime@1.2.4, formidable@1.0.11)

$ matador init tt1
installing Matador into tt1
Success!

$ cd tt1
$ npm install matador
matador@1.1.5-beta ./node_modules/matador
+-- colors@0.6.0-1
+-- klass@1.2.2
+-- valentine@1.5.5
+-- uglify-js@1.3.2
+-- hogan.js@2.0.0
+-- soynode@0.1.4
+-- optimist@0.3.4 (wordwrap@0.0.2)
L-- connect@2.3.3 (bytes@0.0.1, fresh@0.0.1, range-parser@0.0.1, cookie@0.0.3, crc@0.2.0, debug@0.7.0, qs@0.4.2, mime@1.2.4, formidable@1.0.11)

/srv/www/tt1# node server.js

module.js:337
throw new Error("Cannot find module '" + request + "'");
^
Error: Cannot find module '/srv/www/tt1/server.js'
at Function._resolveFilename (module.js:337:11)
at Function._load (module.js:279:25)
at Array.0 (module.js:484:10)
at EventEmitter._tickCallback (node.js:190:38)

As expected, because there is no server.js in tt1 dir

/srv/www/tt1# dir
all node_modules

so, I need to enter the 'all' dir to run the server

$ cd all
$ node server.js
matador running on port 3000
soynode: Compile error
execvp(): No such file or directory

/srv/www/tt1/node_modules/matador/src/matador.js:431
throw err
^
Error: Error compiling templates
at ChildProcess. (/srv/www/tt1/node_modules/matador/node_modules/soynode/lib/soynode.js:177:18)
at ChildProcess.emit (events.js:70:17)
at maybeExit (child_process.js:362:16)
at Socket. (child_process.js:467:7)
at Socket.emit (events.js:67:17)
at Array.0 (net.js:335:10)
at EventEmitter._tickCallback (node.js:190:38)

[davidbyttow]

Huh, interesting. I wonder why you're not getting a server.js. Might have to pull in some help on this one.

~/dev/scratch david$ node -v
v0.6.18

~/dev/scratch david$ sudo npm remove matador -g

~/dev/scratch david$ sudo npm install matador -g
/usr/local/bin/matador -> /usr/local/lib/node_modules/matador/bin/matador.js
matador@1.1.5-beta /usr/local/lib/node_modules/matador
├── colors@0.6.0-1
├── klass@1.2.2
├── valentine@1.5.5
├── uglify-js@1.3.2
├── hogan.js@2.0.0
├── optimist@0.3.4 (wordwrap@0.0.2)
├── connect@2.3.3 (bytes@0.0.1, fresh@0.0.1, range-parser@0.0.1, cookie@0.0.3, crc@0.2.0, debug@0.7.0, qs@0.4.2, mime@1.2.4, formidable@1.0.11)
└── soynode@0.1.4

~/dev/scratch david$ matador init tt1
installing Matador into tt1
Success!

~/dev/scratch david$ cd tt1

~/dev/scratch/tt1 david$ ls
app     server.js

~/dev/scratch/tt1 david$ npm install matador
matador@1.1.5-beta ./node_modules/matador
├── colors@0.6.0-1
├── klass@1.2.2
├── valentine@1.5.5
├── uglify-js@1.3.2
├── hogan.js@2.0.0
├── optimist@0.3.4 (wordwrap@0.0.2)
├── connect@2.3.3 (bytes@0.0.1, fresh@0.0.1, range-parser@0.0.1, cookie@0.0.3, crc@0.2.0, debug@0.7.0, qs@0.4.2, mime@1.2.4, formidable@1.0.11)
└── soynode@0.1.4

~/dev/scratch/tt1 david$ node server.js
matador running on port 3000

[tiberule]

I think it's a system based problem.
on Debian 6 'matador init' command doesn't work as expected. it copies files from '/src/all/' to the new dir including 'all' subdir.
it's easy to fix it by adding '*' to cp command. here it is:
/bin/matador line 9

    exec('cp -R ' + __dirname + '/../src/all/* ' + path, function (err, out) {

now '$ matador init tt1' creates the app skeleton properly. But i'm not sure about the internal content.
Please upload somewhere the properly generated content, I'll try to diff it with my results.