Error 500 in production mode on Windows
#84
Comments
|
It's a bug. And a nasty one at that. The only workaround that I can suggest, is to work in dev mode for the time being 😦 |
|
Updating the title to reflect it's running on Windows. |
|
@lmarkus |
|
yes that is the env variable. By default app runs in dev mode. You will have to force set it to production if you want to check it out in that mode. |
|
Correct, it's NODE_ENV. Just in case, because you specifically said (And as poornima said, if it is not set, it's defaulting to |
|
I tried both production and development mode for NODE_ENV , in both nodejs code and set command of cmd. |
|
To be able to run in production mode you must first have to run grunt build.
|
|
@alexsantos I have run grunt build and templates got fill in .build/templates and public/templates directory Express |
|
That error happened to me on production mode every time the grunt build Alex 2014/1/14 debajyotisarma notifications@github.com
|
|
I tried both npm start runs without errors but faced template error when hit localhost:3000. console logMicrosoft Windows [Version 6.1.7601] C:\Users\deba.jyoti>cd gitcode\frontend\click2call C:\Users\deba.jyoti\gitcode\frontend\click2call>npm start
Multipart body parsing will be disabled by default in future versions. To enable, use |
|
Did you see the error about layouts/master?
|
|
@debajyotisarma instead of setting the |
|
@lmarkus what is the command to set NODE_ENV in windows7 ? |
|
You can do it via GUI exactly as you described, or from the command line (one time use): you can then |
|
@lmarkus Whats the farther step to debug this? |
|
Make sure you have the latest versions of Kraken and generator-kraken (both 0.7.0) You should NOT see this message about memory sessions: Visit http://127.0.0.1:8000/ If that still fails, can you list the error message again, and also the contents of your |
|
@lmarkus [So removing my previous post and created https://github.com//issues/107] |
|
@debajyotisarma Just to note, you don't actually need to set your I'm glad this seems like it was resolved. My guess is that you had some dust issue preventing it from rendering given the Are we okay to close this out then? |
|
@jeffharrell |
|
The original issue remains open, until we address krakenjs/makara#22 @debajyotisarma, so the generated app works correctly. This means that it's an issue specific to something in your more complex application. Can you point me to a github repo that I can clone, and reproduce the problem with? |
|
It looks like from the commentary on krakenjs/makara#22 that you have a solution in mind. PR that? |
ghost
assigned
|
Fixed via Your update should match https://github.com/paypal/generator-kraken/pull/50/files fullname: function (filepath) {
var path = require('path'),
name = path.basename(filepath, '.dust'),
//Hardcoded to forwards slash on purpose. This is due to the way that grunt handles globbing.
//Patterns like **/*.dust are always expanded using '/' with no consideration to the host OS
//separator. This caused issues when trying to build on win_32
parts = filepath.split('/'),
fullname = parts.slice(3, -1).concat(name);
//Hardcoded to forwards slash on purpose. Keeps compatibility on win_32
return fullname.join('/');
} |
Hello,
I have
Error 500in production modeMy test:
I'm on Win 7 64b.
First, I have created a new project in
D:\nodejs\wwwwith kraken:I go in
D:\nodejs\www\testProductionand start appIn Chrome, I go to
http://localhost:8000/and i seeHello, testproduction!It's OK
Secondly, I stop node and I set NODE_ENV:
I build with grunt:
I restart node, I go to
http://localhost:8000/and i seeError 500 ...Is a bug or have I forgot anything?
The text was updated successfully, but these errors were encountered: