Skip to content
Sudonix

sudonix

NodeBB v3 Chat Very Slow

Moved Performance
Posts 47 Posters 3 Views 4.8k Watching 1
Log in to reply

7/47

3 May 2023, 20:10

topic:navigator.unread, 40
Threaded Replies
Related Topics
  • Pandaundefined

    Upgrade issues

    Solved Configure nodebb
    47 13 Sept 2023, 06:58
    13 Sept 2023, 06:58
    1
    2 Votes
    2 Posts
    278 Views
    undefined
    Use this code git fetch # Grab the latest code from the NodeBB repository git checkout v3.x git reset --hard origin/v3.x And you will have the latest version without specifying it https://docs.nodebb.org/configuring/upgrade/
  • undefined

    NodeBB socket with CloudFlare

    Unsolved Performance socket cloudflare nodebb
    47 28 Jul 2023, 11:18
    28 Jul 2023, 11:18
    1 Votes
    23 Posts
    4k Views
    undefined
    @DownPW it’s your only realistic option at this stage.
  • Pandaundefined

    SEO and Nodebb

    Performance nodebb seo
    47 4 Jul 2023, 09:11
    4 Jul 2023, 09:11
    2 Votes
    2 Posts
    400 Views
    undefined
    @Panda It’s the best it’s ever been to be honest. I’ve used a myriad of systems in the past - most notably, WordPress, and then Flarum (which for SEO, was absolutely dire - they never even had SEO out of the box, and relied on a third party extension to do it), and NodeBB easily fares the best - see below example https://www.google.com/search?q=site%3Asudonix.org&oq=site%3Asudonix.org&aqs=chrome..69i57j69i60j69i58j69i60l2.9039j0j3&sourceid=chrome&ie=UTF-8#ip=1 However, this was not without significant effort on my part once I’d migrated from COM to ORG - see below posts https://community.nodebb.org/topic/17286/google-crawl-error-after-site-migration/17?_=1688461250365 And also https://support.google.com/webmasters/thread/221027803?hl=en&msgid=221464164 It was painful to say the least - as it turns out, there was an issue in NodeBB core that prevented spiders from getting to content, which as far as I understand, is now fixed. SEO in itself is a dark art - a black box that nobody really fully understands, and it’s essentially going to boil down to one thing - “content”. Google’s algorithm for indexing has also changed dramatically over the years. They only now crawl content that has value, so if it believes that your site has nothing to offer, it will simply skip it.
  • undefined

    Optimum config for NodeBB under NGINX

    Performance nginx performance
    47 3 Feb 2023, 13:45
    3 Feb 2023, 13:45
    3 Votes
    4 Posts
    947 Views
    undefined
    @crazycells hi - no security reason, or anything specific in this case. However, the nginx.conf I posted was from my Dev environment which uses this port as a way of not interfering with production. And yes, I use clustering on this site with three instances.
  • undefined

    v3 & Harmony diary / thoughts / code snippets

    Announcements harmony v3.beta1 nodebb
    47 23 Jan 2023, 18:56
    23 Jan 2023, 18:56
    5
    36 Votes
    55 Posts
    6k Views
    undefined
    @DownPW I see why. The code relies on the existence of [component="topic/quickreply/container"] However, this by definition means that the below has to be enabled [image: 1679077966615-aeef638f-4188-489d-a9f2-f3a26dbca9d8-image.png] It will then work [image: 1679077992245-7fb38631-e0f3-46ef-b652-00929d927b13-image.png] For some unknown reason, this is hidden in Harmony, and only shows if you select it. In v2, it seems that the <section> is deleted altogether in Persona if “Quick Reply” is disabled, meaning it won’t fire as it can’t locate that specific component. The downside is that you might not want the quick reply function, but I think it’s a PITA to scroll up to the top of the post just to reply, so I have it on
  • undefined

    NodeBB slow after DB recovery

    Solved Performance performance nodebb
    47 28 Feb 2022, 17:42
    28 Feb 2022, 17:42
    5 Votes
    1 Posts
    353 Views
    No one has replied
  • undefined

    NodeBB 1.19.3

    Solved Performance nodebb 1.19.3 performance
    47 17 Feb 2022, 10:55
    17 Feb 2022, 10:55
    4 Votes
    33 Posts
    4k Views
    undefined
    @phenomlab I find the problem Mark The error message indicated this path : http://localhost:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=6983dobg16u I change the path url on config.json [image: 1645128773854-47bacc80-f141-41e4-a261-3f8d650cc6f6-image.png] And all it’s good Weird, I didn’t have to change that path before 1.19.3 But this does not prevent the problem from a clean install with Emoji Plugin EDIT: After test, that resolv the problem installation for 1.18.x but not for 1.19.x (I have other error message when I run ./nodebb Setup For resume: NodeJS 16_x with 1.18.x is ok
  • JACundefined

    NodeBB metadata

    Solved Configure nodebb metadata
    47 8 Dec 2021, 16:37
    8 Dec 2021, 16:37
    2 Votes
    4 Posts
    559 Views
    JACundefined
    @phenomlab said in NodeBB metadata: @jac Are you sure ? https://www.google.co.uk/search?q=site%3Astockportcounty.fans&sxsrf=AOaemvLwnaZL-PliU_2dBOg_Eo1pMVhBjg%3A1638982328139&source=hp&ei=uOKwYeatBcOsad3yp7AE&iflsig=ALs-wAMAAAAAYbDwyLBSDcG5XYoFCKwQFhgz94wTxOcV&ved=0ahUKEwjm6dX71NT0AhVDVhoKHV35CUYQ4dUDCAk&uact=5&oq=site%3Astockportcounty.fans&gs_lcp=Cgdnd3Mtd2l6EAM6BAgjECc6CwgAEIAEELEDEIMBOg4ILhCABBCxAxDHARCjAjoRCC4QgAQQsQMQgwEQxwEQowI6BQguEIAEOggIABCABBCxAzoFCAAQgAQ6CAguELEDEIMBOgsILhCABBDHARCvAToICC4QgAQQsQM6BQgAELEDOgsILhCABBDHARDRAzoLCAAQgAQQsQMQyQM6BQgAEJIDUABYySZg0CdoAHAAeACAAW2IAa0NkgEEMjMuMpgBAKABAQ&sclient=gws-wiz Fair enough 🤪🤪.