"Sorry. Unable to access that page" after using Crudss generator to create jobs collection

[pdebaets]

Hi,

I'm following the tutorial video here:

3 Meteoris Crudss Generator
https://www.youtube.com/watch?v=mqmoJCMJzEg&index=3&list=PLkq0XDlLyPbA6y51gLeJSnK419PFFgS5M

After I generate the "jobs" collection with the one field named "title", I receive the "Success generating code!" message. I then wait, and enter "http://localhost:3000/jobs" in the address bar of Chrome. I get the message "Sorry. Unable to access that page". I'm using chrome on Windows 8.1.

when I search through my project (I'm using webstorm), the only place where the string "jobs" is found is in a readme.md file and in folder tests\cucumber\features. It's as if the code was never generated...?

Can you help?

Thanks,

Peter De Baets

[pdebaets]

When building the code, the statement in MugenServer.js in generateRouter function

this.write(path, content);

... seems to be picking up the wrong default path. Here's the error from the server terminal:

I20150507-13:19:24.871(-7)? { [Error: ENOENT, open 'F:\Users\Peter\Documents\Apps Meteor\ledger.meteor\local\build\programs\server\undefined\client\routers\jobs.js']
I20150507-13:19:24.871(-7)? errno: 34,

Can you help?

[pdebaets]

Looks like it is some kind of a windows issue. I think the

process.env.PWD

... statement in MugenServer.js does not return the correct path in Windows environments. When I replace the statement above with a hard-coded path, the code generation works.

Can someone help with a replacement for "process.env.PWD" in Windows?

[radiegtya]

yeah, we currently not supporting windows this time, and ofc You will find another problem if You are developing advance meteor using windows. We'll fixing it when developing in windows is stable enough.

Anyway, thanks for the report

[pdebaets]

What's the other problem that I will find if I am developing advanced meteor using windows?

[radiegtya]

the other problem is you can't developing mobile apps.

[pdebaets]

I see that you've closed this issue, but isn't it still a problem? Other windows users might come along and get stuck like I did.

Maybe I'm not used to the way that github works, but shouldn't you either save this issue for a future fix, or take some action like including the text "Windows not supported" in the readme file, or include a link to the hardcoded workaround above?

[radiegtya]

Good idea @pdebaets. I'll add "Windows not supported" in documentation and in command line, then close the issue.

[snow-summer]

I didn't see a "windows not supported" in the docs, and I'm having the same trouble (also added a comment with the errors I'm receiving on someone else's issue - but they are seeing it on Ubuntu, so it's not just Windows having the problem).

Would this be do-able if it was run in a bash shell?

edit: here's the other issue: #85
I suspect the trouble with role addition is the same as this one, although it's not generating any errors.