What to do with emails on Dev nodebb site ?

Technical Support
  • Hello !

    I have a Prod nodebb site (which works ; cool 😉 ) and I make all my tests/changes on a Dev one on my local machine.

    I copy Prod to Dev site without problem (adjusting config.json etc...). But what adjustments do you recommend for emails ? How to do them from command line ? I don't want users to receive emails from my Dev system...

    On drupal, I have a module which catches emails on Dev to prevent their sending (it is activated in a settings file ; I can see what would have been sent). On nodebb, can we do the same thing ? Can we activate this from command line or from a file ? (It would be great to have a setting about email sending in config.json to simply change the behavior depending on the Prod or Dev system, like on drupal...). Or can we redirect all mails to one address for tests ?

    I suppose nodebb developpers have a solution for this (they don't send emails to every users from their development machine and can test their mail system 😉 ).

    (Precision, in case it would be necessary for the answer : I use mailgun stmp on my nodebb Prod).

  • Finally, I made my own plugin with hook filter:email.modify. I activate it when on Dev and it redirects all emails to a special email address (to control things).

    Sorry for the "noise"... 😊

  • Hi, do you know the plugin on a tick like on facebook?


Suggested Topics


  • NodeBB Assets - Object Storage

    Unsolved Technical Support
    0 Votes
    98 Posts
    3k Views

    @phenomlab the postbuild script will only run when you execute ./nodebb build via npm run build as that has the logic to execute the postbuild step. The postbuild script should probably be modified to only sync the build/public folder after the initial sync. There should be no need to sync public with every build unless the version of nodebb changes. All new uploads would already be stored in the S3/R2 bucket by the s3 upload plugin.

    So a npm run build init for the initial sync that includes all static assets, and then just npm run build that only syncs the rebuilt assets such as templates , plugins etc.

  • 2 Votes
    5 Posts
    340 Views

    Sorry for the delay. The hovering pagination block may not work as expected, but I think the pagination at the bottom of the page should work fine:

    image.png

  • NodeBB Upgrade Error

    Solved Technical Support
    0 Votes
    5 Posts
    190 Views

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

  • 0 Votes
    28 Posts
    2k Views

    @keng-her Thank you. I'll back everything up and try that and report back.

  • ./nodebb status

    Technical Support
    0 Votes
    2 Posts
    249 Views

    @Abhinov-Singh-0 I suggest learning about solving Linux permissions issues on your own.

    For now, I'm guessing you need to make it executable:

    chmod +x ./nodebb

    It may also be an issue with ownership, in which case you'd use chown.

    You can search for any of these topics and find hundreds of tutorials.