Nodebb on cloud 9

[drubio]

Better, this is my public instance: http://c9.io/sherlockproject/nodebbpublic

[bentael]

• do u have ssh access?
• if not, do you have some sort of a local client that you use to do things, (similar to the heroku toolbelt) where you can: heroku logs --app nodebb for example
• if not how do you see logs?
• how do you deploy?
• does c9 expose port 4567
• what happens if you run it on port 80?

EDIT: wait I just noticed you have that terminal on the bottom, how much power you got in there? I can't help without access

[bentael]

holy shit, c9 is awesome! i just created an account and Im playing with a little bit. wow.

[drubio]

not, do you have some sort of a local client that you use to do things, (similar to the heroku toolbelt) where you can: heroku logs --app nodebb for example
if not how do you see logs?
how do you deploy?
does c9 expose port 4567
what happens if you run it on port 80?

I think I have ssh access, but I was using that terminal (not too powerful... :S)
I don't have idea about logs...
I deploy as the wiki said https://github.com/designcreateplay/NodeBB/wiki/Installing-NodeBB-on-Cloud-9
I think doesn matter the port because c9 redirects to 80 anyway.

I will try different options.

Thanks

[drubio]

@bentael said:

holy shit, c9 is awesome! i just created an account and Im playing with a little bit. wow.

I know!!! I want to use it!!

[bentael]

I think doesn matter the port because c9 redirects to 80 anyway.

@drubio actually it does, it did some testing and looks like 4567 doesn't work.
humor me, try port 8080

[bentael]

also, in case they are assigning ports on the fly, try this:

• edit app.js line: 73'ish if you're running a different version the master now, find this line
• nconf.set('url', nconf.get('base_url' ) + (nconf.get('use_port' ) ? ':' + nconf.get('port' ) : '' ) + nconf.get('relative_path' ));
• and put this line right above it: nconf.set('port', process.env.PORT);

[julian]

also, in case they are assigning ports on the fly,

AFAIK, Heroku does this too.

[bentael]

@drubio just for you, #nohomo, i setup NodeBB on c9 and a free redis instance on redistogo.com

I can confirm my workaround works, c9 doesn't like you choosing which port or address to use, (maybe I can Pull-Request a fix in the NodeBB src for this) but you MUST use the process.env.PORT and process.env.IP

so what I did and it worked was:

• find app.js line 73'ish, right before nconf.set('url', nconf.get('base_url' ) + (nconf.get('use_port' ) ? ':' + nconf.get('port' ) : '' ) + nconf.get('relative_path' ));
• add these two lines:

        nconf.set('port', process.env.PORT);
        nconf.set('bind_address', process.env.IP);

this will enforce the usage env vars instead of config.json ones.

it's working, it's slow as shit, but it works.. https://demo-project-c9-bentael.c9.io/ see!

[julian]

Nice work @bentael! Maybe you can add a guide to setting up NodeBB on Cloud9

[bentael]

that's hacky guide, NodeBB should support ENV VARs for ALL configs. https://github.com/designcreateplay/NodeBB/issues/871

[bentael]

@drubio there might be a fix soon, this is a temp pull request, https://github.com/designcreateplay/NodeBB/pull/872, ill update here again once the team reaches a solution. I am interested in this issue as well.

[drubio]

Thanks guys!! That works!