NodeBB Plugin and Theme authors
So you're saying you tried setting the x-csrf-token header like this and that didn't help?
When you say your "NextJS app ... rewrites", that's a client-side operation? Everything you're talking about happens in the browser, right?
Have you tried just doing the same requests with fetch instead?
Importing hasn't changed much for a while. You can use the existing plugin with the NodeBB version it specifies and upgrade from there.
If you need documentation on how to write your own exporter (term for what extracts the data from your old forum), that is here: https://github.com/akhoury/nodebb-plugin-import/blob/master/write-my-own-exporter.md
@Chad_Abizeid essentially just import with the NodeBB version the plugin says to use, then upgrade from there.
You selected mongo as your database but the instructions you linked install redis. If you wish to use mongo you'll need to install it and start the service. If you wish to use redis, you'll need to start the service and then select redis during setup.
@DownPW I'm highly doubtful that setting the alt tag makes a difference. Where did you test it?
@DownPW what is your URL in config.json? It must exactly match the URL at which you access the site in your browser.
There is already a maximum width. I think it's around 1000px on the .container class.
@daniel-coscione It seems the default docker-compose was made to use another container for routing - it uses expose for port 4567, which means it will be accessible to other containers but not the host machine.
If you want to use local nginx (without containerizing it) or another reverse proxy you can add this to nodebb service configuration:
ports:
- '127.0.0.1:4567:4567'
If you want to use a containerized reverse proxy instead then you'll need to add it as a service to docker-compose. For example you can look at this guide to set up Traefik: https://doc.traefik.io/traefik/user-guides/docker-compose/basic-example/ (just note that you'll need to add traefik.http.services.nodebb.loadbalancer.server.port=4567 label to nodebb service since that is the port NodeBB will be listening on). They also have some docker-compose exmaples with TLS from Letsencrypt.
While it's not a good idea, you can also expose NodeBB by itself by just using the same ports directive as with local reverse proxy, but without binding to localhost:
ports:
- '4567:4567'
It's there a reason you're on such an old version?
