I hear ya and I feel ya. I know this is old, but I went through the same thing, but never gave up because that's what development is. I took one look at it, and said this is something I want - so keeping it under development until most quirks were worked out - was what we have been doing. The maintenance mode feature is handy. You are right about plugins, but trial and error tells you what to use and what not to use - it's not different with wordpress. Some of the plugins, utter crap. This is an amazing opensource - opensource (yes I repeated myself) - GNU licensed - We can do what we want with it but keep in mind that there are two main contributors and you know how long it took you just to configure it? Well look back a few years and see how long this has taken 2 folks to develop. I see amazing things happening with this software. NodeJS has now become hollywood so Joyent has a few extra bucks to make sure that the bugs are worked out of Node as a whole. Node is buggy in general but it's also intuitive and at least npm tells you where the issues are so you can go in and correct them. I know your intent here was simply to vent some frustrations - but unless your a dev - you probably won't be installing this software anyhow :=). I will tell you I will soon be abandoning wordpress for NodeBB - why? It's fast as hell, community oriented, and you have complete and utter freedom to develop without all the intricacies of php and the wp-api (which has always existed) - now it's just JSON REST API buzzwordded up. we just started using this at www.mysimpleclouds.com - brand new - haven't done a darn thing to it and have generated over 250k hits in 3 days - this is post the 10 installations -

FYI - Cluster redis. Use a few ports/sockets. Throw nginx in there, and watch your logs. YOu will know what to fix down to the line and column. Hope this helps!

yo yo - so - i'm digging this software big time. i was posting late at night yesterday bc I'm officially obsessed. I have it running hard on nginx and redis - had to drop the varnish config for it - it was getting cached wayyyy to hard with my setup already.

Anyway my question is about you guys - have you thought about moving into the investment realm yet? Angel.co or angel list - kickstart etc.? I think you have got something here. Only suggestion is to watch the plugins that are being put out.

I'd be willing to get a few campaigns going for you guys - (opensource of course) if you want. Let me know.

I was thinking about using npm to write a few provisioning builds using the plugin dev plugin (that sounded weird as hell) - but was having issues with it - I can totally see one click deploys of like 1000 different stacks/software packages. I'm not a front end guy so I often rely on other people's stuff to build what I want. I wish I was more creative.

Is the graph on the admin side accurate? I took the server down yesterday because I wanted to map out a perfect deploy for this with nginx and a few other packages. Anyway let me know if you guys are interested in "selling out." Node was just bought for quite a bit and this is definitely (in my opinion) other than ghost - the number 1 reason nodejs and npm are so great.

If you want, feel free to share the config above - works with redis - not mongo - which is fine with me bc I prefer redis all day anyhow. it's 30 times quicker and smarter in my limited experience with mongo - you know it picked up the data i already had in mongo and I didn't even do anything :-). This could have been the forever logs - but I have no idea - node is new to me - but i'm starting to really like it.

Would you happen to have your upstart script that you use to keep your forums going on reboot? Or method that you use? Like specific - that will be the icing on the cake for me.

got it

haha same here bro. i'm still at it lol. i don't have much experience with varnish either - honestly i had a preconfigured bash script take care of that side for me - originally just to see how much of an improvement there was.

initially i couldn't get redis configured properly - old version - then I added chris/leo/redis-server repo and ran apt-get update && apt-get upgrade and bang got redis running now. I don't know mongo at all - never used it - only was using it to get this running lol. i literally just made sure that ports matched up on everything for the proxy pass to varnish (in the server block).

But I ran a few benchmarks and I swear varnish has kicked up performance to a whole new level. I've been reading and it's actually not too tough - raul bansel will say do it all with nginx - i'm starting to disagree lol. it's a bit more of a configuration setup but my motto isn't to reinvent the wheel - it's to use it, tweak it, add to it, and do what you want after that :-).

I'm not finished configuring yet - but i was able to get it running with nginx/redis off port much easier (with another instance) but no varnish. we will see what happens.

I actually never had the port in there to begin with. I did put "use_port" = false, in there and the url is there too.

Did you see my config? I'm solid with nginx - so i'm banging my head here. varnish is new to me but that performance boost is incredible. I'll take a look at the docs again - but i've been going through the pdf version with a fine tooth comb and not sure where i'm going wrong here.

That's my config above - both varnish - config.json - and nginx included. I actually don't use apache -

Default port is set to 8080 which is how i have the server block setup for forum.mysimpleclouds.com - you can see everything at the pastebin link above. I posted my entired configuration there.

I thought about adding an additional block to the fqdn however since it's wordpress it's just going to complicate things being as it's php and not nodejs/javascript. It was easier to setup another vhost.

I'm new to nodejs - and love nodebb - since i first set my eyes on it i wanted it. you guys did a great job. I tested it out with docker then decided to bring it live because I loved it so much. I see so much potential in this - way more than forum software. Plus it's so fast with varnish/nginx that i'm literally going to be replacing my wordpress sites one by one - once i figure out how to get it to survive reboots. Looking at upstart scripts / forever - but can't seem to nail that down yet.

I am ultra proficient with NGINX - so a proxy setup is nothing new to me - and I have some pretty advanced nginx configs setup for clients/our own sites but it's a whole new ball game with node. I'm stumped. I spent almost 24 hours getting it up and going with mongo /nginx/varnish - and then finallly got it off the port and was like wtf. Take a look at my setup and let me know if you see anything wrong there. I followed your docs and added a couple things for performance boosts but other than that, this is a pretty simple setup at this point.

FYI I don't use Apache - it's bloat to me and not needed imo. I only use it when I absolutely have to. NGINX powers everything we use.

So i have setup nodebb on a vps running wordpress, nginx, varnish, and nodebb is using mongo - i know nothing about mongo - i just know it's less resource intensive and it's object oriented. i can login when i use the port (4567) - i can access teh domain withou a port - however any attempt to login on the domain without the port fails. same login works with the port.

registration is also forbidden on the naked domain. however works fine with the port. it took me all day to get this setup with varnish and nginx with existing wp install without using redis and i'm stumped. i love this software - i almost gave up on it for discourse bc it just works but i don't like how much of a hog it is. any help would be appreciated. thanks! fyi you can see my config on pastebin here:
link text

my apologies - i nailed it. for anyone with issues - dm me @carlcdavid on twitter for my solution - Especially if your config is similar to mine and you were going through the same issues. (not installed on a fresh vps - nginx, redis - with hhvm as there is a separate wp site - as well as docker).

I have tried every trick in the book - replicating my environment with a snapshot on digital ocean - fresh install onto ubuntu droplet... one click deploy of node on DO... Docker install onto an ubuntu droplet with node. manual installation of node/npm on a clean droplet. my result every time is what your about to see:

same on aws.

the only time i have installed this without error was on a DO droplet that's been up and running for a long time. - running wordpress and nginx - with hhvm and redis - it's full ssl - no wildcard cert - can't afford it - i have a md cert but don't run anything but nginx so that won't solve the ssl issue. one per ip - unfortunately.

i did manage to get it up and running on ip and port. here is my config where it was installed successfully without a single error - (bear in mind that this server was already running, configured, etc) - i would keep it and create another vhost for it - but it will not under any circumstance allow a domain to resolve to it... first the failure output after adding your repo (i'm assuming repo is yours) - and running apt-get update && apt-get dist
ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:43:28)
gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:46:29)
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:57:16
gyp ERR! stack at Object.oncomplete (evalmachine.<anonymous>:108:15)
gyp ERR! System Linux 3.13.0-57-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /root/myNodebbApp/nodebb/node_modules/heapdump
v0.10.37node -v-
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
npm WARN engine [email protected]: wanted: {"node":">=0.10.40"} (current: {"node":"0.10.37","npm":"1.4.28"})
npm WARN engine [email protected]: wanted: {"node":">=0.10.40"} (current: {"node":"0.10.37","npm":"1.4.28"})

[email protected] install /root/myNodebbApp/nodebb/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/utf-8-validate
node-gyp rebuild

gyp ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:43:28)
gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:46:29)
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:57:16
gyp ERR! stack at Object.oncomplete (evalmachine.<anonymous>:108:15)
gyp ERR! System Linux 3.13.0-57-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /root/myNodebbApp/nodebb/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/utf-8-validate
gyp ERR! node -v v0.10.37
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
npm WARN optional dep failed, continuing [email protected]

[email protected] install /root/myNodebbApp/nodebb/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/bufferutil
node-gyp rebuild

gyp ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:43:28)
gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:46:29)
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:57:16
gyp ERR! stack at Object.oncomplete (evalmachine.<anonymous>:108:15)
gyp ERR! System Linux 3.13.0-57-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /root/myNodebbApp/nodebb/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/bufferutil
gyp ERR! node -v v0.10.37
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
npm WARN optional dep failed, continuing [email protected]

[email protected] install /root/myNodebbApp/nodebb/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/utf-8-validate
node-gyp rebuild

gyp ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:43:28)
gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:46:29)
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:57:16
gyp ERR! stack at Object.oncomplete (evalmachine.<anonymous>:108:15)
gyp ERR! System Linux 3.13.0-57-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /root/myNodebbApp/nodebb/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/utf-8-validate
gyp ERR! node -v v0.10.37
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
npm WARN optional dep failed, continuing [email protected]

[email protected] install /root/myNodebbApp/nodebb/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/bufferutil
node-gyp rebuild

gyp ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:43:28)
gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:46:29)
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:57:16
gyp ERR! stack at Object.oncomplete (evalmachine.<anonymous>:108:15)
gyp ERR! System Linux 3.13.0-57-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /root/myNodebbApp/nodebb/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/bufferutil
gyp ERR! node -v v0.10.37
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
npm WARN optional dep failed, continuing [email protected]

[email protected] install /root/myNodebbApp/nodebb/node_modules/mmmagic
node-gyp rebuild

gyp ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:43:28)
gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:46:29)
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:57:16
gyp ERR! stack at Object.oncomplete (evalmachine.<anonymous>:108:15)
gyp ERR! System Linux 3.13.0-57-generic
command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /root/myNodebbApp/nodebb/node_modules/mmmagic
gyp ERR! node -v v0.10.37
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
\

[email protected] install /root/myNodebbApp/nodebb/node_modules/lwip
node-gyp rebuild

gyp ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:43:28)
gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:46:29)
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:57:16
gyp ERR! stack at Object.oncomplete (evalmachine.<anonymous>:108:15)
gyp ERR! System Linux 3.13.0-57-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /root/myNodebbApp/nodebb/node_modules/lwip
gyp ERR! node -v v0.10.37
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is most likely a problem with the heapdump package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls heapdump
npm ERR! There is likely additional logging output above.

npm ERR! System Linux 3.13.0-57-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "--production"
npm ERR! cwd /root/myNodebbApp/nodebb
npm ERR! node -v v0.10.37
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0

I don't know how or why i was able to get it running on this host - only on a port and ip without any error - i just rebooted and i'm not thinking it's going to survive... but we shall see. i was correct - did not survive - yes i installed forever globally as well. so back to square one. rm all files and try again. wordpress survived the reboot - however nodes did not. stumped. vhost on nginx -

server {
listen 80;

server_name forum.example.org;

location / {
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header Host $http_host;
    proxy_set_header X-NginX-Proxy true;

    proxy_pass http://127.0.0.1:4567/;
    proxy_redirect off;

    # Socket.IO Support
    proxy_http_version 1.1;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";
}

}

my config for config.json was:

the minimal config specified in the documentation - specified hostname for nodes - and left everything else alone other than ports required for nodes to run on the redis server that I already was running. db number was changed to 1 rather than 0. however it did not survive the reboot. even with forever - not sure why. i'm currently trying with mongo instead - which I've never used. will keep you posted... when it comes to nginx i can do just about anything - so when i was unable to get a domain to resolve to the proxied host - i was stumped. Node/NPM are new to me - but i like the package management features - i also tried on another server running nginx with varnish - on ubuntu 12.04 its. no go. i love this project - which is why I want it so badly - i can get discourse up but i think that nodebb is much more resource conscious - and it's gorgeous - you guys did a good job - i just wish I could get it going. fyi any fresh install - complains about redis in the end. i have shell scripts i run to configure my servers with the latest version of redis - so anyone going through the tut on a fresh ops is gonna bang there head against a wall - i always run it with hhvm and nginx - that's my stack and when i'm feeling frisky i have a script for varnish config too. Anyway to get to the point - here is my config.json - you can see that node bb is running here:

{
"url": "http://192.241.150.42",
"secret": "don't mess around or i'll hack your grandmas underwear",
"database": "redis",
"redis": {
"host": "127.0.0.1",
"port": "6379",
"password": "about grandmas underwear - i'll hack your girlfriend's",
"database": "0"
}
}

have i changed the ip address to a domain and configured nginx accordingly - yes. i can't get it off a port nor can i get a domain to resolve there. no matter what. best i can do is ip and port.