I figured it out from going through the code. I guess hidden groups are deliberately not populated in userGroups. Seems like it'd be helpful to have an extra flag for groups that determines whether or not it's selectable as a title aside from hidden (maybe I don't want the group or list of members to be available publicly but still want to use the associated title) but it might be too much of a corner case for me. For now, I've unhidden the groups that I really needed and made sure to disable join requests on them.
RoiEXLab last edited by
I installed nodebb according to the docs behind an nginx reverse proxy.
When nodebb is started using the systemd, the log-protocol at /admin/advanced/logs stays empty.
Any ideas why this is?
Thanks in advance!
teh_g last edited by
@RoiEXLab I ran into the same thing and never came to a satisfying solution. I suspect it is due to the systemd logs not writing to where the admin page expects logs to be. On top of that, I think systemd logs are permission limited.
This is something I noticed too; off the top of my head, this could probably be solved by using
teein the systemd script, so you output to both
stdout(where systemd expects output) and the log for nodebb (where nodebb would read it)
Yep that works, I updated my version here: