Flarum Node Chat?

0E800

https://github.com/Ardnived/flarum-chat-server
^
Has anyone gotten this to work? I didn't see it in the extensions area.

I have been experimenting with Nodejs chat projects. It would be nice if one used the same auth.
So flarum username == chat user name

This is what I have so far.
https://chat.keys-daggers.org
Using:
https://github.com/IgorAntun/node-chat

AngelAvila

It's seems pretty cool. May I ask: What would it be useful for?

I mean, nowadays, there are lots of easier ways to have like a Chat for your community. In my case, I have an IRC server connected to my website and my gaming servers, and also everything is connected to Discord and viceversa.

0E800

I was thinking more of a chat / pm combo.

I found this tutorial for Laravel:
http://itsolutionstuff.com/post/laravel-52-chat-message-module-using-socketio-redis-express-and-nodejs-from-from-scratchexample.html

However I am not sure how different Laravel is from Flarum.

What I would like is:
User creates account on Flarum.
Clicks on 'Chat' link and is auto signed into chat.
User can /msg or /pm another user and that user receives a notification that includes the message.

I also thought about just using IRC, maybe in a iframe, but would rather it all be Flarum.

I think if I was more familiar with php and laravel that I would be able to modify laravel tutorials to work for Flarum. I could also just be naive.

Ill check out discord but again, I want to keep all my eggs in the same basket. I thought discord was just another forum framework/saas.

tlalok

@0E800 We have build a node chat for my community, authentication with flarum.

You can fork here : https://github.com/mondediefr/mondedie-chat

0E800

Thank you tlalok Just what I was looking for.

Quick question:
Where do I find the Cookie_Secret and Session_Secret?

Or is that something I make up myself?

Create .env file in project root with this content :

ENV=production
COOKIES_SECRET=xxxxxxxxxxx
SESSION_SECRET=yyyyyyyyyyy
FLARUM_API_ENDPOINT=http://domain.tld/api/

Edit: Never-mind, I answered my own question:

PORT Port app optional 5000
FLARUM_API_ENDPOINT API URL required none
COOKIES_SECRET Set random cookies secret required none
SESSION_SECRET Set random session secret required none
REDIS_URL Redis instance ip/hostname required none
PIWIK_ID Piwik id optional none
PIWIK_URL Piwik url optional none

tlalok
Update2:
So I am getting this error. I must be doing something wrong with that session and cookie secret:

Erreur 500
secret option required for sessions

Error: secret option required for sessions
    at session (/var/www/keysndaggers/chat/node_modules/express-session/index.js:199:12)
    at Layer.handle [as handle_request] (/var/www/keysndaggers/chat/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/var/www/keysndaggers/chat/node_modules/express/lib/router/index.js:312:13)
    at /var/www/keysndaggers/chat/node_modules/express/lib/router/index.js:280:7
    at Function.process_params (/var/www/keysndaggers/chat/node_modules/express/lib/router/index.js:330:12)
    at next (/var/www/keysndaggers/chat/node_modules/express/lib/router/index.js:271:10)
    at cookieParser (/var/www/keysndaggers/chat/node_modules/cookie-parser/index.js:56:14)
    at Layer.handle [as handle_request] (/var/www/keysndaggers/chat/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/var/www/keysndaggers/chat/node_modules/express/lib/router/index.js:312:13)
    at /var/www/keysndaggers/chat/node_modules/express/lib/router/index.js:280:7
    at Function.process_params (/var/www/keysndaggers/chat/node_modules/express/lib/router/index.js:330:12)
    at next (/var/www/keysndaggers/chat/node_modules/express/lib/router/index.js:271:10)
    at /var/www/keysndaggers/chat/node_modules/express-validator/lib/express_validator.js:351:5
    at Layer.handle [as handle_request] (/var/www/keysndaggers/chat/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/var/www/keysndaggers/chat/node_modules/express/lib/router/index.js:312:13)
    at /var/www/keysndaggers/chat/node_modules/express/lib/router/index.js:280:7

tlalok

0E800 Or is that something I make up myself?

Yes, you must generate a random character string.
ex : https://github.com/mondediefr/mondedie-chat/blob/master/dev.yml#L13-L14

0E800

tlalok

So edit

dev.yml

and

.env

and make the session_secret and cookies_secret the same / match?

When you say 'generate' a random string, am I using a tool to generate it? Or can I just make up something like "mysecret"

Here is my .env:

ENV=production
COOKIES_SECRET=
SESSION_SECRET=
FLARUM_API_ENDPOINT=https://keys-daggers.org/api/

tlalok
Not sure what I am doing wrong. Why its unable to find the secrets. Thank you for your help.

0E800

tlalok

I think maybe my Nginx config might be causing the issues.

This is what my Nginx error log shows:

[error] 3281#3281: *1 connect() failed (111: Connection refused) while connecting to upstream, client: (myip), server: chat.keys-daggers.org, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:5000/", host: "chat.keys-daggers.org"

Here is my sites-enabled config:

server {
    listen    80;
    server_name    chat.keys-daggers.org;
#    rewrite ^(.*)  https://chat.keys-daggers.org$1 permanent;
        return https://$host$request_uri;
}

server {
    listen 443 ssl http2;
    listen [::]:443 ssl http2;
    include snippets/snakeoil.conf;
    include snippets/ssl-params.conf;
    server_name chat.keys-daggers.org;

    ssl on;
    ssl_session_cache shared:SSL:10m;
    ssl_session_timeout 5m;
    keepalive_timeout 60;


location / {
proxy_pass http://127.0.0.1:5000;
proxy_redirect off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_max_temp_file_size 0;
client_max_body_size 50m;
client_body_buffer_size 256k;
proxy_connect_timeout 180;
proxy_send_timeout 180;
proxy_read_timeout 90;
proxy_buffer_size 16k;
proxy_buffers 4 64k;
proxy_busy_buffers_size 128k;
proxy_temp_file_write_size 128k;
}
}

When I run
node app.js
I get:

express-session deprecated req.secret; provide secret option app.js:33:15

Kyrne

0E800 I would remove those keys from your post, they can be used to do a number of things to your site that you don't want

jordanjay29

Kyrne 0E800 I removed those secret keys for your safety.

0E800

Kyrne jordanjay29

Thank you guys for your concern. I just threw those numbers up as an example. I wanted to make sure the length of the string was not the issue.

Be well.

jordanjay29

0E800 Ahh, you can just note that next time and I'll ignore it. Just trying to make sure people don't get compromised just for seeking support.

datitisev

0E800 express-session deprecated req.secret; provide secret option app.js:33:15

That just means req.secret is deprecated. The NodeJS app should still run fine until req.secret gets removed, probably in Express 5, whenever that comes.

About the Nginx... I don't know, sorry. However, I wish you good luck. ?

Kulga

0E800

0E800 [error] 3281#3281: *1 connect() failed (111: Connection refused) while connecting to upstream, client: (myip), server: chat.keys-daggers.org, request: "GET / HTTP/2.0", upstream: "http://127.0.0.1:5000/", host: "chat.keys-daggers.org"

proxy_pass http://127.0.0.1:5000;

Nginx being a reverse proxy for something? What is supposed to be listening at port 5000?

0E800

datitisev

Thanks mang.
Ive been pounding my head against this for 3 days now. Wish someone would try to get it to work and show me what I am doing wrong.

I feel like I am doing everything correctly. Arrrg. Guess ill just wait.

BTW datitisev
I seen you here:
https://www.npmjs.com/package/node-flarum
Is this something different?

datitisev

0E800 BTW datitisev
I seen you here:
https://www.npmjs.com/package/node-flarum
Is this something different?

Yeah, FlarumJS was going to be my big project, however I decided helping out Flarum itself would be more beneficial for me and everybody else.
https://discuss.flarum.org/d/2121-flarum-with-nodejs-mongodb-discontinued/29