There are a couple pokestops I can hit from my desk at work, if the GPS is a little dodgy...
NOOO! Do we have pokemons in the source code!
Hey @medwards -- Indeed, that's what we're hoping to do with search. Not everyone wants to use Reds, so I'm actually planning on divorcing Reds from core, and allowing third-party plugins to interface with the routes.
@a_5mith True, but honestly, it's easier to set up a quick Linux VM (and I say this as someone who is not at all a fan of Linux) and the support is far better.
The same occurs for myself as well. I'm running the latest version on the GitHub. I've disabled all the plugins and it still occurs. However, on this forum, it seems to work fine.. interesting.
My console reads this:
WebSocket connection to 'wss://community.*.net/socket.io/?EIO=3&transport=websocket&sid=NQaX7qjgJhYbzRiiAAAT' failed: Error during WebSocket handshake: Unexpected response code: 400
Thanks for the support guys. ❤
You'll probably want NodeBB to run in the foreground, and not pipe output to the log file, if you want to use forever or upstart.
node loader.js --no-silent --no-daemon will run production mode and leave output piping to stdout. It will also run in the foreground, which forever expects.
If you use app.js, you won't need --no-daemon, but you'll only be running one process.