Community

It's a little difficult to explain, but at a high level, we're a single page app, which means when you click on an anchor, we request the JSON for the new page, render the html on the user browser, empty everything in #content, and inject it into #content. The overlay is a transition that makes this process a little smoother.

We use a templating engine called Benchpress to render templates on both server and client-side.

@julian said in Cannot start nodebb with systemd:

/opt/nodebb/logs/output.log

Hi julian, sorry for my delay response.
I changed the services as you suggested, essentially this was my first implementation.

I removed the file output.log, then I rebooted the system and started the services, when I went in the logs folder the file output.log was empty.

UPDATE:

I used journalctl -fu nodebb.service to see the log of the service, and I discovered a nice thing:

alt text

Any idea?

UPDATE 2 [FIXED]

Okay, so after spending some times on this, I discovered what is the cause of the problem. Essentially, I have installed nodebb as root account (which is wrong, my bad), and the systemd service was configured to run nodebb as the user "sfarzoso", but that user was not the owner of nodebb folder, so when I started the service using systemd, a permission problem happen.

For fix this, I chowned the "opt" folder for "sfarzoso", which is the folder that I need to install nodebb, then I cloned the repo of nodebb and launched the setup again.
All works now.

Thanks for the attention, king regards.