Skip to content
Sudonix

restarting nodebb on boot

Unsolved Configure
3 2 1.0k 1
  • Pandaundefined

    I have asked this question on the nodebb forum but still very confused, if I may also take opinions here.
    In a power cut or glitch my server may restart. What is the best way to make nodebb forum come back up without doing manual start?
    I was looking at nodemon which I understand, but the nodebb docs suggest a method of adding somethings to a systemd file !
    Its more complicated, is it a better method or can I just run nodebb under nodemon for auto restarts?

    phenomlabundefined 2 Replies
    0
  • Pandaundefined Panda

    I have asked this question on the nodebb forum but still very confused, if I may also take opinions here.
    In a power cut or glitch my server may restart. What is the best way to make nodebb forum come back up without doing manual start?
    I was looking at nodemon which I understand, but the nodebb docs suggest a method of adding somethings to a systemd file !
    Its more complicated, is it a better method or can I just run nodebb under nodemon for auto restarts?

    phenomlabundefined

    @eeeee Have you seen / read the below?

    https://docs.nodebb.org/configuring/running/

    Mark
    Founder - Phenomlab Ltd

    Executive Technology & Security Leadership

    0
  • Pandaundefined Panda

    I have asked this question on the nodebb forum but still very confused, if I may also take opinions here.
    In a power cut or glitch my server may restart. What is the best way to make nodebb forum come back up without doing manual start?
    I was looking at nodemon which I understand, but the nodebb docs suggest a method of adding somethings to a systemd file !
    Its more complicated, is it a better method or can I just run nodebb under nodemon for auto restarts?

    phenomlabundefined

    @eeeee said in restarting nodebb on boot:

    can I just run nodebb under nodemon for auto restarts?

    It’s a better method. Nodemon just looks for file system changes and would effectively die if the server was rebooted meaning you’d have to start it again anyway. Systemd is the defacto standard which is how the operating system interacts in terms of services, scheduled tasks etc.

    Mark
    Founder - Phenomlab Ltd

    Executive Technology & Security Leadership

    1
Log in to reply

Related Topics
  • Pandaundefined

    Nodebb and emails

    Solved Configure nodebb
    27
    5 Votes
    27 Posts
    4k Views
    phenomlabundefined
    @Panda it will use SMTP. In all cases, I never use any plugin to send email. I’ll always send it raw.
  • JACundefined

    NodeBB recent cards customisation

    Solved Customisation nodebb recent cards
    3
    1
    2 Votes
    3 Posts
    713 Views
    JACundefined
    @phenomlab thank you very much for the assistance Mark, massively appreciated as always. The great thing about this is it’s all documented for other NodeBB users that come looking for solutions . Looks far better .
  • cagatayundefined

    NodeBB v3 Chat Very Slow

    Moved Performance nodebb v3 nodebb chat
    47
    11 Votes
    47 Posts
    11k Views
    phenomlabundefined
    @DownPW Seems fine.
  • Pandaundefined

    adding some console.log to Nodebb

    Solved Customisation nodebb
    4
    1 Votes
    4 Posts
    1k Views
    phenomlabundefined
    @eeeee if you’re using the console, you could try node app.js > app.log 2>&1 This would redirect stdout to a file named app.log and redirect stderr to stdout. I’m not sure about standard logging under NodeBB, but there is an error log located at logs/error.log. Failing that, you could always stop the NodeBB service then use ./nodebb dev from the console which would then provide debug output.
  • mventuresundefined

    NodeBB: Opening the Composer for replies

    Solved Configure cms composer
    2
    0 Votes
    2 Posts
    696 Views
    phenomlabundefined
    @mventures Quick reply is basically exactly that. However, it’s possible to trigger the full composer as below [image: 1681314389744-82ca1209-31be-4a51-a641-9887b5a238b8-image.png] Failing that, you’ll need to use the reply button in the sticky toolbar [image: 1681314442570-1d230bcb-ff8e-4756-94f7-6e2fb7a94bc4-image.png]
  • mventuresundefined

    NodeBB: Upgrading to NodeBB v3.x

    Solved Configure nodebb v3.x
    6
    0 Votes
    6 Posts
    1k Views
    phenomlabundefined
    @mventures You’d need to connect to the server and execute it directly - not on your local terminal. Review the guide below, which will show you how to gain access via SSH to your server https://docs.ovh.com/gb/en/dedicated/ssh-introduction/ Once you have access, you’ll need to navigate to the actual folder where NodeBB is installed You’ll then need to change to the directory as shown below /home/unbuntu/nodebb [image: 1680448167972-fdffe673-bf63-4b6d-a728-5506fddc1aff-image.png] In most cases, initial access takes you to the root of the file system. You can always issue pwd in a Linux terminal which will show you the Present Working Directory. From there, you can issue the command cd /home/ubuntu/nodebb Once in the NodeBB directory, you’d use the below commands ./nodebb stop git fetch && git checkout develop && git reset --hard origin/develop ./nodebb upgrade ./nodebb start Line 1 stops the NodeBB instance Line 2 gets the latest files from GIT (repository) and then checks out the development branch. It then resets the version you are using to the development branch ready for v3 Line 3 Runs the upgrade once the new branch is set, and code pulled Line 4 Restarts the NodeBB instance after the upgrade has completed Note that when you restart NodeBB and log back in, things will look very different to what you had in v2.
  • cagatayundefined

    Podcast Share NodeBB

    Solved Configure podcast nodebb
    15
    4 Votes
    15 Posts
    2k Views
    phenomlabundefined
    @cagatay You could experiment with nodebb-plugin-ns-embed but I expect the x-origin tag on the remote site to prevent playback.
  • marusakyundefined

    Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    2k Views
    phenomlabundefined
    @marusaky based on the work completed thus far (in relation to PM exchanges), I’m going to mark this completed. Sending email from the server itself works fine without issue, and DNS appears to be clean (valid SPF, DMARC, and DKIM records). It appears that only Gmail marks incoming messages from your domain as spam - perhaps because of the domain age, which there is nothing we can do to prevent this. Mail delivery to all other domains appears to work fine in al of my tests.