Skip to content

Custom html in nodebb to prevent cache

Unsolved Configure

Related Topics
  • nodebb loading emojis

    Solved Configure
    16
    1 Votes
    16 Posts
    679 Views

    @DownPW sure. Let me have a look at this in more detail. I know nginx plus has extensive support for this, but it’s not impossible to get somewhere near acceptable with the standard version.

    You might be better off handling this at the Cloudflare level given that it sits in between the requesting client and your server.

  • Upgrade Problem from 2.8.3 to 2.8.4

    Solved Configure
    35
    8 Votes
    35 Posts
    2k Views

    @cagatay No, you can ignore that.

  • restarting nodebb on boot

    Unsolved Configure
    3
    1 Votes
    3 Posts
    323 Views

    @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.

  • Gettin Erors NodeBB

    Solved Configure
    7
    0 Votes
    7 Posts
    451 Views

    @phenomlab no forum is working goods.
    there is no eror message since yestarday.

  • Fresher in Nodebb install

    General
    24
    15 Votes
    24 Posts
    2k Views

    @Hari I’ve been reading a lot about APO. Looks impressive.

  • Adding fileWrite to nodebb code

    Solved Configure
    16
    5 Votes
    16 Posts
    788 Views

    @eveh this might be a question for the NodeBB Devs themselves. In all honesty, I’m not entirely sure without having to research this myself.

  • Plugin reaction Bug

    Solved Customisation
    15
    0 Votes
    15 Posts
    945 Views

    @DownPW That was going to be my next suggestion 🙂

  • Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    995 Views

    @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.