Will the planned writeable API include a login / logout (optional Register account) function?

I need something like that to call via PHP or PHP rendered code (JS if client side), because oauth isn't a useable Option.

I like NodeBB. It's beautiful, clean and lightning fast

NodeJS based is fine for a communication tool like a forum or a chat, but as cms / cmf I prefer a php base.
So a bridge between NodeBB and CMS is needed.

So, how NodeBB could interact or integrated (cms layout with embedded NodeBB, shared login via cms or nodebb api) with a php application?

A plugin to add custom profile fields in admin panel would be fine.

I tested some forum software to find the "best one" and so I also tested esoTalk

It based on php instead of nodejs. EsoTalk forum is different to php forum software like smf or phpbb. It's fat free and really fast.

• conversation list with channels and filter option instead of category view (channel = category = tag)
• private conversations (share topic with users and groups only) could be an alternative to private messages and maybe also chat
• A blog post about 10 hidden features like multiple channel filter, private or group conversation, ...

NodeBB is already modern and full of new ideas, but public / private / group conversations and some other esoTalk approaches could also improve NodeBB any more?

I think when a hashtag is used in a post it should be added as topic tag. So users can add tags simple during write a new post...

Hi @Normando ,
still the same error.

2019-12-30T14:17:45.061Z [4567/92] - error: [authentication] TypeError: Cannot read property 'useAuthorizationHeaderforGET' of undefined
    at Object.OAuth.getStrategy [as method] (/usr/src/app/node_modules/nodebb-plugin-sso-nextcloud/library.js:115:22)
    at /usr/src/app/src/plugins/hooks.js:121:29
    at /usr/src/app/node_modules/async/dist/async.js:1635:13
    at replenish (/usr/src/app/node_modules/async/dist/async.js:444:21)
    at /usr/src/app/node_modules/async/dist/async.js:449:13
    at eachOfLimit$1 (/usr/src/app/node_modules/async/dist/async.js:475:34)
    at awaitable(eachOfLimit$1) (/usr/src/app/node_modules/async/dist/async.js:208:32)
    at eachOfSeries (/usr/src/app/node_modules/async/dist/async.js:662:16)
    at awaitable(eachOfSeries) (/usr/src/app/node_modules/async/dist/async.js:208:32)
    at Object.reduce (/usr/src/app/node_modules/async/dist/async.js:1634:16)

Hi,
any hint about that error? I'm new with oauth...

2019-12-28T16:22:30.805Z [4567/58] - error: [authentication] TypeError: Cannot read property 'useAuthorizationHeaderforGET' of undefined
    at Object.OAuth.getStrategy [as method] (/usr/src/app/node_modules/nodebb-plugin-sso-nextcloud/library.js:115:22)
    at /usr/src/app/src/plugins/hooks.js:121:29
    at /usr/src/app/node_modules/async/dist/async.js:1635:13
    at replenish (/usr/src/app/node_modules/async/dist/async.js:444:21)
    at /usr/src/app/node_modules/async/dist/async.js:449:13
    at eachOfLimit$1 (/usr/src/app/node_modules/async/dist/async.js:475:34)
    at awaitable(eachOfLimit$1) (/usr/src/app/node_modules/async/dist/async.js:208:32)
    at eachOfSeries (/usr/src/app/node_modules/async/dist/async.js:662:16)
    at awaitable(eachOfSeries) (/usr/src/app/node_modules/async/dist/async.js:208:32)
    at Object.reduce (/usr/src/app/node_modules/async/dist/async.js:1634:16)

Is there a plugin repository to browse?
Looks like not all plugins available in nodebb admin are compatible / working.
So a repository with plugins and compatible nodebb version info would be nice.

@Staff
After some more debugging I found the config.json file inside of the "/usr/src/app" directory, which prevents the image to update the nodebb app by pulling a new image...

Any change to get the config.json moved to a sub directory "config"? Or wouldn't work nodebb inside of a docker container that way?

If I restart the running nodebb container it would work, but docker swarm respawn a new container to the first one after I manually restart it...

Also tested to add the install directory as volume if there would be changes after web install is finished, but same problem.
Each time a new container is spawned I get the web installer again...

It would help to now WHY I get the installer each time and how to solve that with the nodebb/docker image (with additional persistent volumes)?

Hi,
I tried to run nodebb/docker with a redis db as swarm / stack.

compose:

version: '3.7'
services:

  nodebb:
    image: nodebb/docker
    networks:
      webproxy:
      redis:
    labels:
      # caddy swarm reverse proxy with lets encrypt
      caddy.address: "nodebb.example.com"
      caddy.targetport: '4567'
      caddy.log: '/ stdout "[{host}] {remote} - {user} [{when}] \"{method} {uri} {proto}\" {status} {size}"'
      caddy.errors: "stdout"  
    stdin_open: true
    tty: true         
    volumes:
      - build:/usr/src/app/build
      - uploads:/usr/src/app/public/uploads
    deploy:            
      restart_policy:  
        condition: any 
        delay: 10s     
        max_attempts: 5
        window: 60s

  redis:
    image: redis:5.0.7
    networks:
      redis:
    volumes:
      - data:/data
    command: 'redis-server --appendonly yes'  
    

networks:
  webproxy:
    external:
      name: proxy_webproxy
  redis:

volumes:
  data:
  build:
  uploads:

After setup is finished I click the "Launch" button and that kills the container:

2019-12-28T11:54:49.017Z [19] - info: [build] Asset compilation successful. Completed in 140.239sec.

     

NodeBB Setup Completed. Run "./nodebb start" to manually start your NodeBB server.

Starting NodeBB
    "./nodebb stop" to stop the NodeBB server
    "./nodebb log" to view server output
    "./nodebb restart" to restart NodeBB

Would be no problem because of swarm restart_policy a new container should start...
But after that I get the installer again instead of the installed nodebb forum.

So something seems to be wrong. Redis DB is empty and nodebb volumes contains data.
See below:

rancher:/var/lib/docker/volumes# ls -lh nodebb_*/_data/
nodebb_build/_data/:
total 12
-rw-r--r--    1 root     root          11 Dec 28 11:54 cache-buster
drwxr-xr-x    2 root     root        4.0K Dec 28 11:33 export
drwxr-xr-x    7 root     root        4.0K Dec 28 11:53 public

nodebb_data/_data/:
total 132
-rw-r--r--    1 999      ping      129.8K Dec 28 11:52 appendonly.aof

nodebb_uploads/_data/:
total 20
drwxr-xr-x    2 root     root        4.0K Dec 28 11:25 category
drwxr-xr-x    2 root     root        4.0K Dec 28 11:25 files
drwxr-xr-x    2 root     root        4.0K Dec 28 11:25 profile
drwxr-xr-x    2 root     root        4.0K Dec 28 11:25 sounds

So how to install with persistent data?

Why no redis data is written to the volume?
I'm new with redis, but it should work without password because I haven't set an password?
Redis connect works fine from nodebb to redis container:

root@a8dd26787f8f:/usr/src/app# telnet redis 6379
Trying 10.0.19.2...
Connected to redis.
Escape character is '^]'.
quit
+OK
Connection closed by foreign host.

@Austin-Benesh
Would be great to have compose und files / images!
Is it configurable by container environment or (external / mapped) files are needed?

Some more docker / compose documentation would be nice. How to deploy und upgrade, persistent data and how to configure (ideally by environment)?

Hi,
I'm searching for a forum software with push notification support which works with closed browser.
That is possible with web push api and service worker as shown here:

ststimac, aliams, molant

Push Notifiations Demo

Push notifications can help you achieve what apps have long been able to do. Join us as we explore how to build the front-end and back-end of a push notification

That example isn't pinned to FCM, MCS or WNS and it used the push service based on the browser / device.

If the plugin is still compatible it should be added a service worker to get offline / closed browser notifications working.

@trevor
Filtered channels and private conversations are a great approach, but I think NodeBB won't go that way in the future.
So esoTalk is an alternative to NodeBB because it's also fast and comfortable to use.

The combination with all the benefits of both would be the absolute best solution...