Best posts made by markkus
RE: Putting a NodeJS webapi onto the same server as NodeBB
Well... If you already have NodeBB running on port 80 without nginx/Apache proxy, then you can not assign another service on the port as well. I recommend you to set up an nginx/Apache proxy for NodeBB and create virutal hosts for each service you want to run on port 80 (this way you can run multiple services/sites on port 80).
RE: [nodebb-plugin-shoutbox] Shoutbox plugin
Great plugin! Anyway, I know that this plugin isn't confirmed to be compatible with 0.4.1, but I've found a bug.
When a non logged-in user browses the forum and then returns to the page where the shoutbox is located, it will display an empty page to the user.
Grabbing avatars from an external URL
I'd like to know if there exists a method to alter the way how avatars are automatically assigned to users (like Gravatar). For example, let's say I have an user named Foo and his avatar is located on a remote server & domain, on the URL domain.com/avatar/Foo.png. Basically, all I need is that NodeBB would automatically take the avatar from a specified URL and assign it as the user's avatar when he/she registers for the first time.
RE: Question regarding multiple instances of NodeBB on dedicated server
You can't run multiple NodeBB instances on the same port (4567), so each instance should have its own port assigned (and different system path too). As for setting up the proxy, I suggest you to use nginx. Each instance should have its own nginx virtual host set up which then routes to the corresponding NodeBB instance.
However, I'm not sure about the database. Maybe you can run all the instances on the same Redis db, maybe not...
RE: Some problem with plugins
If you are using
nodebb-plugin-emoji-extendedthen there is a 'dirty' fix for that.
Navigate to your Emoji plugin folder and open
Once you've opened the file, find a part where it states
Set this to something like this
Of course, this will only work if you are running NodeBB with nginx or Apache proxy.
RE: Issues with Redis
I managed to fix the problem by uninstalling the
redis-serverservice that I had installed via
apt-get& manually installing the latest redis stable build which has an updated config to allow supervisors like
systemdto supervise the process.
To anyone who's encountering the same issues, here's a decent tutorial on how to get Redis up and running on Ubuntu 16.04.