Skip to content
Sudonix

restarting nodebb on boot

Unsolved Configure
3 2 1.9k 1
  • Panda
    Panda
    Panda
    wrote on
    #1

    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?

    phenomlab 2 Replies
    0
  • Panda 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?

    phenomlab
    phenomlab
    phenomlab
    wrote on
    #2

    @eeeee Have you seen / read the below?

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

    Mark Cutting also advises organisations as a Fractional CIO, Fractional CISO and Executive Advisor, helping boards improve technology governance, cyber resilience and executive decision making. Learn more at Gratmore Ltd

    0
  • Panda 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?

    phenomlab
    phenomlab
    phenomlab
    wrote on
    #3

    @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 Cutting also advises organisations as a Fractional CIO, Fractional CISO and Executive Advisor, helping boards improve technology governance, cyber resilience and executive decision making. Learn more at Gratmore Ltd

    1
Log in to reply

Related Topics
  • cagatay

    What’s going on with NodeBB?

    Performance nodebb script die
    20
    8 Votes
    20 Posts
    6k Views
    phenomlab
    @cagatay The most reliable way to upgrade Node.js on Ubuntu depends on how you originally installed it. Method 1: Using NVM (Recommended) If you already use Node Version Manager (NVM), upgrading is simple. NVM allows you to keep both versions and switch between them if needed. Install Node 22: nvm install 22 Switch to Node 22: nvm use 22 Set it as your default: nvm alias default 22 Verify the change: node -v Method 2: Using NodeSource (PPA) If you installed Node.js via apt using the NodeSource repository, you need to update the repository script to point to the new version. Remove the old NodeSource list (optional but cleaner): sudo rm /etc/apt/sources.list.d/nodesource.list Download and run the NodeSource setup script for Node 22: curl -fsSL [https://deb.nodesource.com/setup_22.x](https://deb.nodesource.com/setup_22.x) | sudo -E bash - Install/Upgrade Node.js: sudo apt-get install -y nodejs Verify the installation: node -v Method 3: Using the ‘n’ Package If you have npm installed, you can use the n interactive manager. Clear the npm cache: sudo npm cache clean -f Install the ‘n’ helper: sudo npm install -g n Install Node 22: sudo n 22 Update your shell: hash -r Troubleshooting Permission Denied: If you see permission errors using Method 2 or 3, ensure you are using sudo. Path Issues: If node -v still shows version 20 after upgrading via NVM, restart your terminal or run source ~/.bashrc. Conflicts: Avoid mixing these methods. If you switch from apt to nvm, it is best to sudo apt remove nodejs first to avoid path conflicts.
  • Panda

    What is this bar called?

    Solved Customisation nodebb
    92
    1
    36 Votes
    92 Posts
    42k Views
    DownPW
    This is good
  • mventures

    NodeBB: Opening the Composer for replies

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

    NodeBB: hCaptcha

    Solved Configure hcaptcha
    15
    2 Votes
    15 Posts
    4k Views
    phenomlab
    @mventures none that I know of. I don’t recall selecting these either for mine.
  • crazycells

    optional "snow falling" theme

    Solved Customisation nodebb
    6
    6 Votes
    6 Posts
    2k Views
    phenomlab
    @Sala ok, but that’s still the same loop which is going to have an impact on the CPU.
  • cagatay

    Podcast Share NodeBB

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

    NodeBB templates

    Locked Chitchat themes templates nodebb
    12
    4 Votes
    12 Posts
    5k Views
    phenomlab
    Placing this here for reference https://sudonix.com/topic/216/nodebb-js-script-css-theme-switcher Further information and posts can be found at this link
  • JAC

    Iframely (Nodebb)

    Solved Configure
    40
    4 Votes
    40 Posts
    17k Views
    phenomlab
    @DownPW This is now resolved. The issue was an incorrect URL specified in the Nodebb plugin. I’ve corrected this, and now it works as intended.