My site goes off

Pablo Macaluso

I make my NodeBB but sometimes the NodeBB goes off.

When i close the Putty console. Site goes off

julian

That's correct, the node application will not continue running after your SSH session is terminated.

Pablo Macaluso

That's correct, the node application will not continue running after your SSH session is terminated.

Take a look at this wiki article!

I read it, but theres anyway to make it runing without the console open?

And, like to use it without port like gippy.com.ar only

trevor

I read it, but theres anyway to make it runing without the console open?

Use forever ...

npm install forever -g
Go to the folder where you installed NodeBB.
Run this command: forever start app.js

Hope this helps.

julian

Yep, that'll do it @trevor

trevor

Additionally, please read the Wiki thoroughly before asking for help. Maybe this will help you as well. It's the best starting point to answer your most simple of questions.

(github.com)

NodeBB Wiki
https://github.com/designcreateplay/NodeBB/wiki

If you absolutely can't figure it out, then your best bet would be to ask your question here.

Pablo Macaluso

I get errors

julian

Looks like you'll need to install forever:

sudo npm install -g forever

trevor

Step by step. It should be working now.

Pablo Macaluso

Looks like you'll need to install forever:
sudo npm install -g forever

It works! i forget the sudo!! im soooo sorry.

I need to remove the ports. I read the wiki and didint find nothing

psychobunny

You can setup your NodeBB to use port 80, if you're on port 80 you can access the forum via the url without having a port

Either edit via

nano config.json

or run node app --setup again and configure it. In general you would need to run NodeBB via sudo to gain access to port 80, and if you have something else listening to port 80 (ex. apache) this will not work. I know that @OutlawedOffroad recently managed to figure this out!

Steve

or run node app --setup again and configure it. In general you would need to run NodeBB via sudo to gain access to port 80, and if you have something else listening to port 80 (ex. apache) this will not work. I know that @OutlawedOffroad recently managed to figure this out!

Here's the thread with my back and forth battle with this.. I'm on CentOS 6.4 so your miles may vary:
http://try.nodebb.org/topic/282/might-as-well-add-another-cog-to-my-plan-im-on-cent-os-64

Still a work in progress. We fixed the issue then uncovered additional issues.. Once we complete it all and everything is aces I'm going to ask server support for a rundown of what they did since a lot of trial and error. Hopefully populate that Wiki link that goes nowhere with some info.