Weird, that fixed it. I assumed that since the URL was exactly the same whether I ran it with ./nodebb start or ./nodebb dev, it couldn't be related to cache. I suppose I just don't know enough about how caches work.
Thanks anyways 😛
Hello I have a problem I can't get NodeBB running on 0.5.1 branch. Everything is up-to-date and I have the latest version from the branch.
When I run
./nodebb dev/watch/start it crashes at the end just before the ready.
This is the error, it seems that loader.js doesn't like callback.
info: [meta/css] Minifying LESS/CSS info: [meta/css] Done. info: [meta/templates] Compiling templates info: [themes] Successfully compiled templates. child_process.js:1023 throw new Error('Unknown signal: ' + sig); ^ Error: Unknown signal: SIGCONT at ChildProcess.kill (child_process.js:1023:11) at ChildProcess.<anonymous> (c:\wamp\www\Github\NodeBB\loader.js:32:35) at ChildProcess.emit (events.js:98:17) at handleMessage (child_process.js:322:10) at Pipe.channel.onread (child_process.js:349:11) Auré[email protected] /c/wamp/www/Github/NodeBB (0.5.1)
Vanilla theme is also up-to-date I don't really know what's going on.
Eh, does windows not support the SIGCONT signal? sigh...
It seems like so
This could help
Not to worry, I'm not using
SIGCONT in the traditional sense, just as a way to signal the NodeBB child app that it can bind to the expected port.
@julian You just need to find another way thanks to Windows
@julian Yes I can, I don't see if I'm on 0.5.1 though. What are the key features to see it ?
(I've searched for sub-categories but didn't see them).
You'll need to also check out the 0.5.1 branch of the vanilla theme as well.