nodebb + heroku + mongolab
-
Or if you really want get it set up in the meantime, use it with redis, like the docs suggest
-
The best method to get on with your way is to detail every step you've taken (along with the log output from that step)
This way we can look at ex. Step 3 and go "aha! That's where it broke" etc.
-
My error logs are often flagged as 'spam', BTW:
.node-gyp/5.0.0/common.gypi not found (cwd: /Library/node/node_modules/mongodb/node_modules/mongodb-core/node_modules/kerberos) while reading includes of binding.gyp while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error:gyp
failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/Library/node/node_modules/npm/node_modules/node-gyp/lib/configure.js:357:16)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Darwin 13.4.0
gyp ERR! command "/usr/local/bin/node" "/Library/node/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Library/node/node_modules/mongodb/node_modules/mongodb-core/node_modules/kerberos
gyp ERR! node -v v5.0.0
gyp ERR! node-gyp -v v2.0.2
gyp ERR! not ok -
Once you've gotten the right deps set up (ex. MongoDB or redis, etc)
./nodebb setup
should get you on your way. As mentioned previously paste your logs if it doesn't go as expected -
Sorry, posting on mobile (perhaps I should write an alert that tells the user a new post has been created... It works on desktop, not on mobile yet)
Can you post the step by step log I mentioned earlier?
-
Yeah I guess you're running into uncharted territory. The guide is for redis not mongo. I might clear some time next week to figure it out (if you're patient enough to wait) and write a new guide.
The other option is to contact heroku and ask, I know that they're pretty responsive on helping nbb installs.
-
@psychobunny said:
(if you're patient enough to wait)
TBH, I was hoping to get it done in 24 hours with no sleep.
-
@reid said:
You seem to be taking a very negative stance on NodeBB based on your inability to install it.
My first impression is that it IS impossible to install it. Most people would probably have resigned after 12–18 hours of not getting it to work. First impressions matter. I guess most OSX users wouldn't be able to change their drive to a different OSX version either, as according to the instructions ONLY Mavericks macs can install this forum (within the OSX family).
I'd say I've been very, very patient and enduring.
-
@meh said:
@psychobunny said:
(if you're patient enough to wait)
TBH, I was hoping to get it done in 24 hours with no sleep.
It's doable so up to you if you value sleep if you figure it out it would be great if you'd write / edit the heroku guide
-
I'll see what I can do. In any case, I could perhaps provide some input to your upcoming OSX / Heroku / Mongolab chapter
Edit: My final input for your OSX install guide is in the top post. I would advice to make the installation meant for the Cloud platform independent of the user's choice of computer. He wants to use this thing in the cloud, simple as that, and not at home on his little machine.
-
Everything about the Mongo DB files and settings are still very unclear. Plus there are no hints as to what to do or try, just faffing about and hoping for the best. I don't even have a mongodb.conf file anywhere on my computer. Maybe stretching into the 36 hours straight.
Adding:
"mongo": "~0.10.1", "connect-mongo": "~2.0.0"
to package.json, but I have no idea what I'm doing or why that would work.