Is this plugin dead @bri? Should I look to use something else?

@qqqqqqq said in Amazon Document DB instead of MongoDb:

@julian wait you support postgresql? not listed here https://docs.nodebb.org/configuring/databases/

Just outdated docs then. It has been supported for years.

I wrote a install guide for NodeBB 1.15 with postgresql on Fedora 33 back in 2020.
https://www.mangolassi.it/topic/22497/setup-nodebb-on-fedora-33-with-postgresql-and-nginx-with-https-only

@julian said in Which is better NodeBB or Discourse?:

@scottalanmiller said in Which is better NodeBB or Discourse?:

@pitaj said in Which is better NodeBB or Discourse?:

Nodebb-plugin-import can help

What formats does it support?

Lots! https://www.npmjs.com/search?q=nodebb-import-*

@julian I have a small NodeBB instance that has been running since 2014. It was setup back then on redis. I've kept it up to date over the years and it is running on v2.8.7 right now, but it is still redis.

I'd like to move away from redis since this is no longer (for years now) the recommended way to install and run nodebb. Sadly, I can find no way to convert the nodebb redis database to postgresql or mongodb that works. Sure, it is a small lightly used private community, but I would like to keep things current.

1. Can I use a version of nodebb-import to import from another nodebb?
2. Is nodebb-import forever stuck on v1.12.1 (per https://www.npmjs.com/package/nodebb-plugin-import)
   That seems like a huge leap to upgrade from 1.12.1 to current just to import.

Obviously, a db conversion tool would be simple, but nothing ever came of those tools as they were only compatible with specific versions and I kept my system too up to date for them to be useful.

@JaredBusch said in How can I migrate from redis to postgresql/mongodb:

Found a pull request for nodebb-plugin-import that gives it postgresql capability.

Well, it seem that I cannot install v1.12.1 as required by this plugin.

npm never successfully builds.

[jbusch@obelisk nodebb]$ sudo -u nodebb ./nodebb setup
package.json not found.
Populating package.json...
OK
Dependencies outdated or not yet installed.
Installing them now...

npm notice 
npm notice New minor version of npm available! 8.3.1 -> 8.12.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v8.12.2
npm notice Run npm install -g [email protected] to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/pg
npm ERR!   pg@"^7.4.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer pg@"^8" from [email protected]
npm ERR! node_modules/pg-cursor
npm ERR!   pg-cursor@"^2.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/nodebb/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/nodebb/.npm/_logs/2022-06-18T01_31_52_584Z-debug-0.log
Error installing dependencies!
message: Command failed: npm install --production
stdout: null
stderr: null
/opt/nodebb/src/cli/package-install.js:54
		throw e;
		^

Error: Command failed: npm install --production
    at checkExecSyncError (node:child_process:828:11)
    at Object.execSync (node:child_process:902:15)
    at Object.installAll (/opt/nodebb/src/cli/package-install.js:45:9)
    at Object.<anonymous> (/opt/nodebb/src/cli/index.js:60:18)
    at Module._compile (node:internal/modules/cjs/loader:1103:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
    at Module.load (node:internal/modules/cjs/loader:981:32)
    at Function.Module._load (node:internal/modules/cjs/loader:822:12)
    at Module.require (node:internal/modules/cjs/loader:1005:19)
    at require (node:internal/modules/cjs/helpers:102:18) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 1461,
  stdout: null,
  stderr: null
}
[jbusch@obelisk nodebb]$ 

Built just fine to v2.2.0 though.

[jbusch@obelisk nodebb]$ sudo -u nodebb ./nodebb setup
Dependencies outdated or not yet installed.
Installing them now...

npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.
npm WARN deprecated [email protected]: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: support for ECMAScript is superseded by `uglify-js` as of v3.13.0
npm WARN deprecated [email protected]: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1

added 922 packages, and audited 923 packages in 2m

76 packages are looking for funding
  run `npm fund` for details

5 high severity vulnerabilities

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
OK

2022-06-18T01:40:58.599Z [1600] - info: NodeBB Setup Triggered via Command Line

Welcome to NodeBB v2.2.0!

This looks like a new installation, so you'll have to answer a few questions about your environment before we can proceed.
Press enter to accept the default setting (shown in brackets).

@gotwf said in How can I migrate from redis to postgresql/mongodb:

Still, maybe one of those can be updated and adapted?

Found a pull request for nodebb-plugin-import that gives it postgresql capability.
https://github.com/akhoury/nodebb-plugin-import/pull/240

So I think I will try that an use the "vanilla" import and see what works.

That is a project for the weekend when beer is involved.

@gotwf said in How can I migrate from redis to postgresql/mongodb:

Yeah, but I'd thought I remembered seeing a free one

In our conversation from News Year's Day 2021.

Postgres question

@gotwf said in Postgres question: @julian Being lazy here - Is PostgreSQL a first class db backend for NodeBB these days or is it still third party plugin?...

NodeBB Community (community.nodebb.org)

@gotwf said in How can I migrate from redis to postgresql/mongodb:

Found this 3rd party script here, fwiw:

There are others. None of them have been updated in 2+ years.

@gotwf said in How can I migrate from redis to postgresql/mongodb:

My bad. Seems NodeBB folks offer this for a small fee:

They have for years. I first asked this question years ago when they switched to mongo as default.

@gotwf said in How can I migrate from redis to postgresql/mongodb:

are you not already using PostgreSQL

No, in 2015, the install options were redis or mongo, with redis the actual default. I didn't feel the need to use Mongo as my site would never be large and redis could easily handle it.

@gotwf said in How can I migrate from redis to postgresql/mongodb:

By "normal", are you referencing PHP and MariaSQL here?

By normal, I mean not using the normal NodeBB options that are default today. That means Ubuntu and Mongo according to the docs. https://docs.nodebb.org/installing/os/ubuntu/

Been a year or so since I last posted about this, but now I really need to get off of CentOS 7. I can easily reinstall everything on Fedora 36, but I would like to also get off of redis since the project has changed since I first set this up.

Do I need to give up on NodeBB and move to Discourse or some other backend? I'm not a large site operator, but I've been with NodeBB since version 0.9 or so (November 2015). I like the platform, but I do not like not being on a "normal" design anymore.

Redis was the primary back then, but no longer. I think it would be better if I could convert my system to stay in line with the current install design of NodeBB.

I mean, I an on git v1.19.x (currently 1.19.7) and things still work fine. But for how long will it still work well? Obviously, I need to get off of CentOS 7 because it is causing issues due to old package versions.

@pitaj said in Remove login button:

@jaredbusch you could try something like this in your custom css in the ACP:

a[href="/login"] {
  display: none !important;
}

That did it.

so as a quick test, a little searching in the persona theme source login, I found I could refine it to this.

Build software better, together

GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.

GitHub (github.com)

Then I added a quick inline style command to hide it in those 6 returned locations.

Then there were two place in /templates/partials/menu.tpl that referenced /login. I did the same there.

Would this be simple enough for a theme setting? Obviously not as an inline style.. that was simply the easilet/quickest way to see if hiding those elements worked.

Rebuilt and gone.

@pitaj said in Remove login button:

Easiest way is probably too hide it with CSS.

That is what I was assuming I would need to do. Was hoping though.

Any pointer on the best way to handle it, that will survive upgrades, before I try and break things?

@dogs said in Remove login button:

I search in ACP for "login" but I couldn't find any setting to disable login global on the forum.

Yeah, there never has been.

Is there an easy place to remove the login button from being seen?

Using NodeBB for a small project with only a couple people posting but many public users that will never have login capabilities.

@julian said in Postgres question:

@oplik0 Yes, correct

I mean that the API itself is stable, and that we are not adding arguments and methods willy-nilly, and removing others.

So what about that conversion utility? It definitely worked when I tested taking a system from redis to mongo a couple years ago.

But that was a couple years ago.

@gotwf said in Postgres question:

Good to know.

I had a need to setup a new instance and did not want to use Mongo for similar reasons as to why you were looking at options.

I documented what I did here: https://www.mangolassi.it/topic/22497/setup-nodebb-on-fedora-33-with-postgresql-and-nginx-with-https-only

I want to tinker with that some more.

@gotwf said in Postgres question:

@julian Being lazy here - Is PostgreSQL a first class db backend for NodeBB these days or is it still third party plugin? I'm not up on the latest and greatest.

Well it is built into the ./nodebb setup process now.

I have a tiny site running on it with zero issues.

I would like to convert a small site that is currently on redis to postgresql but it appears that @Ben-Lubar (not tagging he hasn't been online in 2 years) has archived his conversion repo.

@julian will this still work?
https://github.com/BenLubar/nodebb-postgres-converter

Or is there something new?

When executing the initial ./nodebb setup, is there a way to preanswer the questions?

@baris said in Multiple reply buttons on newest nodebb:

The reply button under each post is used to make a direct reply to the post. The blue reply button makes a reply to the topic itself.

It is also not new.