Are there any "official" S3 plugin for NodeBB? there are loads of unmaintained forks of S3 plugins which is quite concerning...

I think it is working now. BTW, I am using a vertical 1080p display.

Late reply, but I used the updated service file and it works.

Menu on top left is not functioning properly:

Navbar/profile menu is not working:

When the browser is narrow, NodeBB community website's theme breaks apart.

Editing window gets hidden:

More to come because I can't minimize the dialog

@sharonyue I do not have a public website, just a local test server. Meili works much better than Solr, but this is not tested on a live, production server.

No, I did not. It worked after I did so. Somehow I missed that obvious section...

Same error

I am upgrading from 2.5.3 -> 2.5.7, and get this error on build:

2022-10-16T15:17:04.734Z [4567/392256] - error: [build] Encountered error during build step
Error: Cannot find module 'progress-webpack-plugin'
Require stack:
- /opt/nodebb/webpack.prod.js
- /opt/nodebb/src/meta/build.js
- /opt/nodebb/src/cli/manage.js
- /opt/nodebb/src/cli/index.js
- /opt/nodebb/nodebb
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
    at Function.Module._load (node:internal/modules/cjs/loader:804:27)
    at Module.require (node:internal/modules/cjs/loader:1028:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/opt/nodebb/webpack.prod.js:5:24)
    at Module._compile (node:internal/modules/cjs/loader:1126:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
    at Module.load (node:internal/modules/cjs/loader:1004:32)
    at Function.Module._load (node:internal/modules/cjs/loader:839:12)
    at Module.require (node:internal/modules/cjs/loader:1028:19)
2022-10-16T15:17:04.735Z [4567/392256] - error: Error: Cannot find module 'progress-webpack-plugin'
Require stack:
- /opt/nodebb/webpack.prod.js
- /opt/nodebb/src/meta/build.js
- /opt/nodebb/src/cli/manage.js
- /opt/nodebb/src/cli/index.js
- /opt/nodebb/nodebb
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
    at Function.Module._load (node:internal/modules/cjs/loader:804:27)
    at Module.require (node:internal/modules/cjs/loader:1028:19)
    at require (node:internal/modules/cjs/helpers:102:18)
    at Object.<anonymous> (/opt/nodebb/webpack.prod.js:5:24)
    at Module._compile (node:internal/modules/cjs/loader:1126:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10)
    at Module.load (node:internal/modules/cjs/loader:1004:32)
    at Function.Module._load (node:internal/modules/cjs/loader:839:12)
    at Module.require (node:internal/modules/cjs/loader:1028:19)

@julian ah, sorry I didn't make it clear. I am looking to integrate with a self-hosted SSO solution, thus the mention of Keycloak and Ory stack.

Is there a maintained plugin that allows using Keycloak as user management? I know there are a few sparsely documented plugins, but they do not seem to be maintained.

Kratos might be another option, but I don't think there is any plugin.

@julian But I still have to rebuild on the production server, right? Unless there is a way to set up CI/CD.

@oplik0 No problem. Thank you for bringing this plugin to life!

At the same time, it might be nice to mention it in the README.

@gotwf I have tried NodeBB (multiple ports) + Postgres + Redis. It is a bit tricky to set up (because I have Nginx serving a bunch of other stuff under subpaths). I don't know if Redis is used for caching in this case, though.

Now, I would really like better systemd integration and S3 uploads...

@phenomlab Webpack has always been slow for me. I have used some newer build systems that use ES6, and man they are blazing fast.

Also glad to see build process optimization seems to be on roadmap, though looks like NodeBB will stay with untyped JS for a long time.

Now, with PHP there is zero build time and some support of static typing, of course.

I am starting NodeBB with systemd:

[Unit]
Description=NodeBB
Documentation=https://docs.nodebb.org
After=system.slice multi-user.target postgresql.service redis-server.service

[Service]
Type=forking
User=nodebb

WorkingDirectory=/opt/nodebb
PIDFile=/opt/nodebb/pidfile
Environment=NODE_ENV=production
ExecStart=/usr/bin/env node loader.js
Restart=always

[Install]
WantedBy=multi-user.target

However, no useful logs are in journalctl. I still have to use ./nodebb log:

$ journalctl -u nodebb -f
Sep 25 11:13:04 home systemd[1]: Starting NodeBB...
Sep 25 11:13:05 home systemd[1]: nodebb.service: Can't open PID file /opt/nodebb/pidfile (yet?) after start: Operation not permitted
Sep 25 11:13:05 home systemd[1]: Started NodeBB.
Sep 25 11:17:52 home systemd[1]: Stopping NodeBB...
Sep 25 11:17:52 home systemd[1]: nodebb.service: Deactivated successfully.
Sep 25 11:17:52 home systemd[1]: Stopped NodeBB.
Sep 25 11:17:52 home systemd[1]: nodebb.service: Consumed 19.344s CPU time.
Sep 25 11:20:19 home systemd[1]: Starting NodeBB...
Sep 25 11:20:20 home systemd[1]: nodebb.service: Can't open PID file /opt/nodebb/pidfile (yet?) after start: Operation not permitted
Sep 25 11:20:21 home systemd[1]: Started NodeBB.

Any idea how to fix it?

@phenomlab The last thing would be... I wish the build process is faster. On my Pi 4 test server it takes a few minutes to build and redeploy, and I would assume on a tiny cloud VM it would be even slower.

@phenomlab I am wary that MongoDB is not fixing its Ubuntu 22.04 install, and in general its support on Community Edition. That's why I would like to use Postgres instead.

Redis might work too, though it might require a heck lot of memory.

@phenomlab Thank you for sharing your experience. It is very helpful to hear from people with experience of both platform.

I am aware that Flarum needs a plugin for everything, but on the other hand, NodeBB has a few critical things lacking for me, so I have to write quite a few plugins too:

1. Upload to S3
2. BBCode support

S3 should be easy, as I might consider forking the ancient S3 nodebb-s3 plugin, though I would hope this support is built in core. BBCode is more problematic, as it might amount to the same effort of writing every plugin I need for Flarum combined. This actually makes NodeBB's set up effort tied with Flarum, for me right now.

Plus, I am not sure if PostgreSQL support is first class in NodeBB, as it is not documented very well. On the other hand, Flarum's DB schema is very clean, so I would say I can always migrate away from Flarum if I really want to, but NodeBB's schema is kind of unique... as it is document based and everything is in jsonb. The reason I am mentioning this is that I don't really want to use Mongo.

nodebb-# \dt
            List of relations
 Schema |     Name      | Type  | Owner  
--------+---------------+-------+--------
 public | legacy_hash   | table | nodebb
 public | legacy_list   | table | nodebb
 public | legacy_object | table | nodebb
 public | legacy_set    | table | nodebb
 public | legacy_string | table | nodebb
 public | legacy_zset   | table | nodebb
 public | searchpost    | table | nodebb
 public | searchtopic   | table | nodebb
 public | session       | table | nodebb
(9 rows)
MariaDB [flarum]> SHOW TABLES;
+----------------------+
| Tables_in_flarum     |
+----------------------+
| access_tokens        |
| api_keys             |
| discussion_tag       |
| discussion_user      |
| discussions          |
| email_tokens         |
| flags                |
| fof_upload_downloads |
| fof_upload_files     |
| group_permission     |
| group_user           |
| groups               |
| login_providers      |
| migrations           |
| notifications        |
| password_tokens      |
| post_likes           |
| post_mentions_post   |
| post_mentions_user   |
| post_user            |
| posts                |
| recipients           |
| registration_tokens  |
| settings             |
| tag_user             |
| tags                 |
| users                |
+----------------------+
27 rows in set (0.004 sec)