Skip to content
Sudonix

sudonix

build nodebb Warning in entrypoint size limit

Solved Performance
Posts 2 Posters 2 Views 321 Watching 1
Log in to reply

1/2

15 Apr 2023, 20:03

Threaded Replies
Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

Related Topics
  • undefined

    NodeBB socket with CloudFlare

    Unsolved Performance socket cloudflare nodebb
    2 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.
  • undefined

    Nodebb design

    Solved General nodebb
    2 11 Jul 2023, 10:13
    11 Jul 2023, 10:13
    1 Votes
    2 Posts
    395 Views
    undefined
    @Panda said in Nodebb design: One negative is not being so good for SEO as more Server side rendered forums, if web crawlers dont run the JS to read the forum. From recollection, Google and Bing have the capability to read and process JS, although it’s not in the same manner as a physical person will consume content on a page. It will be seen as plain text, but will be indexed. However, it’s important to note that Yandex and Baidu will not render JS, although seeing as Google has a 90% share of the content available on the web in terms of indexing, this isn’t something you’ll likely lose sleep over. @Panda said in Nodebb design: The “write api” is preferred for server-to-server interactions. This is mostly based around overall security - you won’t typically want a client machine changing database elements or altering data. This is why you have “client-side” which could be DOM manipulation etc, and “server-side” which performs more complex operations as it can communicate directly with the database whereas the client cannot (and if it can, then you have a serious security flaw). Reading from the API is perfectly acceptable on the client-side, but not being able to write. A paradigm here would be something like SNMP. This protocol exists as a UDP (UDP is very efficient, as it is “fire and forget” and does not wait for a response like TCP does) based service which reads performance data from a remote source, thus enabling an application to parse that data for use in a monitoring application. In all cases, SNMP access should be “RO” (Read Only) and not RW (Read Write). It is completely feasible to assume complete control over a firewall for example by having RW access to SNMP and then exposing it to the entire internet with a weak passphrase. You wouldn’t do it (at least, I hope you wouldn’t) and the same ethic applies to server-side rendering and the execution of commands.
  • undefined

    SEO and Nodebb

    Performance nodebb seo
    2 4 Jul 2023, 09:11
    4 Jul 2023, 09:11
    2 Votes
    2 Posts
    401 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

    Composer Zen icon?

    Solved Configure nodebb
    2 17 Jun 2023, 09:58
    17 Jun 2023, 09:58
    1
    2 Votes
    8 Posts
    459 Views
    undefined
    @DownPW exactly. Not really a new concept, and in all honesty, not something I’ve ever used. If you consider the need to add links and references, or citations, you’d need to be able to see other parts of the screen!
  • cagatayundefined

    NodeBB v3 Chat Very Slow

    Moved Performance nodebb v3 nodebb chat
    2 3 May 2023, 12:08
    3 May 2023, 12:08
    11 Votes
    47 Posts
    5k Views
    undefined
    @DownPW Seems fine.
  • qwinterundefined

    Using nodebb as a publishing destination, posting after git push?

    General nodebb
    2 18 May 2022, 07:34
    18 May 2022, 07:34
    0 Votes
    5 Posts
    686 Views
    undefined
    @qwinter this particular site uses the code I wrote if you want to see it in action. It’s a information and intelligence gatherer I designed for collecting various information security articles from around the globe and consolidating them in one place. Essentially, each “post” is in fact generated by the script, and the NodeBB API. https://hostrisk.com/
  • undefined

    NodeBB 1.19.3

    Solved Performance nodebb 1.19.3 performance
    2 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
  • RiekMediaundefined

    NodeBB Design help

    Solved Customisation
    2 16 Oct 2021, 12:56
    16 Oct 2021, 12:56
    3
    2 Votes
    8 Posts
    1k Views
    undefined
    @riekmedia I’ve applied some new CSS to your site. Can you reload the page and try again ? For the record, this is what I added #footer { background: #2d343e; border-top: 4px solid #2d343e; font-size: 0.9em; margin-top: 70px; padding: 80px 0 0; position: relative; clear: both; bottom: 0; left: 0; right: 0; z-index: 1000; margin-left: -15px; margin-right: -338px; } The /categories page seems a bit messed up, so looking at that currently EDIT - issued some override CSS in the CATEGORIES widget <!--- CSS fix for overspill on /categories page - DO NOT DELETE --> <style> #footer { margin-right: -45px; } </style> That should resolve the /categories issue.