@o-o - I was not able to make fly.io work. Unfortunately I don't remember all the details, but effectively fly.io and NodeBB were working under different assumptions as far as local resources were concerned. Upon idle my fly machine would lose track of the fly database, and upon restart it would attempt to restart NodeBB from scratch. Until the idle everything worked fine. But at the end of the day my issue was automatically serving the precompiled Javascript resources that NodeBB presupposes.

Outsourcing the database to something like S3 might fix the problem. Also, fly.io changes very quickly, and I know others were having the same problems with other frameworks, so they may now have a workaround.

Any updates on this? I know someone who is looking at NodeBB and Discourse, and this could be a deal breaker for them.

NodeBB caters to long-form discussions with things like pagination and the Lavender theme.

Nice! Will this sort of thing make a big difference to the amount of memory that ought to be allocated to the server?

Thanks @PitaJ!

It looks like Express is the way to handle static resources in NodeJS. It looks like they are being set up in <index.js>. I have no idea why the javascript resource is inaccessible.

@phenomlab - Yes, "site" is just a fictional placeholder. There is a separate problem where the app autostops gracefully on SIGINT, but instead of autostarting properly it goes to the NodeBB installation page (link). So the URL and accompanying resources won't be persistent until I figure that out. I just wanted to work out this .js problem first.

I am trying to set up a NodeBB server over at fly.io. After installation I am unable to access nodebb.min.js:

GET https://site.fly.dev/assets/nodebb.min.js?v=beq285jiqim net::ERR_ABORTED 404

Refused to execute script from 'https://site.fly.dev/assets/nodebb.min.js?v=beq285jiqim' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.

I can't access the JS file in my browser at all. Is there a trick to serving resources in NodeJS? I know that in Django serving static files requires some extra work, but since nodebb.min is a compiled file I am really not sure how to address this.

Thanks

I just set up a NodeBB server over at fly.io, and everything was up and running remarkably fast. The only problem is that, by default, I am making use of two fly machines to run the app (the only configuration needed to get NodeBB working was scaling the machines' memory up to 512mb).

The problem is that the VMs are not sharing the node app correctly. It's as if each machine has its own instance of NodeBB. For example, if my request is handled by machine 1 then I am taken to the live forum, but if my request is handled by machine 2 then I am taken back to the NodeBB installation page.

Is it possible to run a NodeBB app between two virtual machines? Or do I need to reconfigure for one?

@brazzerstop said in What's next after v3?:

...it seems to me that this is not the best idea to overload the forum (along with the server) with unnecessary functions like (video conferences, calls, streams, coupons).

Yes: "Jack of all trades, master of none."

It almost seems like a confusion of a website with the web itself. I don't want one website to do every single thing. I go to different websites for different purposes. If a website has no specific purpose, but tries to cater to all purposes, then it effectively ceases to have purpose and direction.

@julian said in What's next after v3?:

Thanks for everybody's comments regarding federation and ActivityPub. I've been steeping myself in the Fediverse for the past week and have been inspired

There is definite potential here.

• I have started a Mastodon account for NodeBB
• I started my own Mastodon server, because I obviously have nothing better to do with my free time

I think a forum variant of Mastodon would be wonderful. The one thing that seems to be missing from these "federated" options is something akin to Twitter's verification system. It seems to me that the larger the scope, the greater the need for verification.

Thanks, @baris!

Okay, thank you, @PitaJ.

Is there a good way to limit a users' or groups' threads or posts? Such as limiting to X threads per week or X posts per day? Or perhaps a workaround for Number of minutes between threads like there is for posts?

Thanks

@phenomlab - Yes, I have tried rebuilding, reinstalling, removing other plugins, and switching to v2.x.

@baris - I do get an error related to <this thread>, but I am not able to locate the config.json file. Has this changed since 2018?

@TheBronx - Before you do anything, let me try to make sure my system is set up correctly. Now I am getting a console error error loading admin/plugins/reputation-rules. I am wondering if the plugin failed to install correctly (although reinstallation didn't seem to help).

@phenomlab - Yes, I was just looking at that now.

There is a console Uncaught ReferenceError: require is not defined at <this line of reputation-rules.tpl>.

There was also a problem with the emoji plugin, but I deactivated that for the time being. I don't know if it was interconnected.

(v2.8.12)

@TheBronx - I actually tried this in both of my test environments, v2.8.12 and v3.1.6, both with MongoDB.

When I open up ACP->Plugins->Reputation Rules all of the fields are always blank.

I must be doing something goofy if no one else is having this problem.

...Oh, I get it now. Usernames are slugified on purpose.

Regarding the search error, it happens specifically on my user named "Complex-x*x+x.x". Search cannot find this user's posts. When I re-open the Posted by input in `nodebb-plugin-dbsearch' that user gets replaced by "Guest".

(v3.1.6)

Does NodeBB distinguish between stable releases and edge releases? Is it just that 3.2, 3.3., 3.4, etc., will be stable releases and everything in between is 'edge'?

Thanks