@Brophy What I do with my custom plugin is

git clone nodebb-plugin-my-plugin into the server user's home folder,
cd nodebb-plugin-my-plugin
npm link

then in the nodebb's root folder: npm link nodebb-plugin-my-plugin. And I never lose the plugin, if I have to release a new update I just do a git pull in the plugin (original) folder, then is updated automatically when I restart the forum.

So in your case I'd say create the nodebb-theme-your-theme folder somewhere in your server, do npm link and then in nodebb npm link nodebb-theme-your-theme .

But I think this is suggested for development environments, not for production, even if in my case is working pretty well
Another way to do it is to install your theme with npm install git+https://git@github.com/<your-git-user>/<your-private-theme-repo>.git

Voted for NodeBB!

@sanatisharif probably is nodebb-plugin-iframely

User.getUidByUsername here

@orweinberger

I think you should configure the S3 Bucket's policies.

I think, but I'm not sure since I just googled it, should be something like:

{
  "Version": "2008-10-17",
  "Id": "preventHotLinking",
  "Statement": [
    {
      "Sid": "1",
      "Effect": "Allow",
      "Principal": {
        "AWS": "*"
      },
      "Action": "s3:GetObject",
      "Resource": "arn:aws:s3:::my-brand-new-bucket/*",
      "Condition": {
        "StringLike": {
          "aws:Referer": [
            "http://yourwebsitename.com/*",
            "http://www.yourwebsitename.com/*"
          ]
        }
      }
    }
  ]
}

AWS Documentation
StackOverflow Question
Little Extra

I think you can contact directly @julian to know how much they take to implement the functionality you want in NodeBB or in a plugin

To anyone searching the same thing, I resolved the problem using the custom write-api hooks, I wasn't aware of:

https://github.com/NodeBB/nodebb-plugin-write-api/blob/master/routes/v1/index.js#L45

filter:plugin.write-api.routes

that gives you data, I used it in this way:

function(data, callback) {

	var app = data.router;
	var apiMiddleware = data.apiMiddleware;
	var middleware = data.middleware;
	var errorHandler = data.errorHandler;

        app.post('/route', apiMiddleware.requireUser, function(req, res) {
        // do stuff
        });

	callback(null, {
		router: app
	});

};

Obviously you should have nodebb-plugin-write-api installed.

I honestly don't know how much RAM it would require, but if you're worried about it you can always use MongoDB + Redis, it's fast enough and it doesn't require to put everything in RAM.

I think big forums use mongo + redis if not only mongo.

My forum has 4k users and 3.5k posts (more or less) and I use 84Mb of RAM with Redis only, if we suppose that an user "weight" as much as a post (even if a post is actually less), it would require 3.5Gb of RAM (311k/7.5k*84).
Even if I think it should be less.

@jiangcaiyang He gets notification of the same "event" every time he scrolls at the bottom of the page /notifications

@Esteban-Constante by socket you can create a new socket handler in your plugin (and it can use the same function as the one you already use for the api route more or less), check here how they create a new "socket route", and here how they use it for the Q&A plugin.

Here is how they do for actual mentions (you probably already saw it)

You can just use the User.setUserField(uid, field, value, callback) function, by importing the module.parent.require('./user')

To set the value while creating the account, I suggest you to check the custom registration field (or something like that) plugin and use it, or taking inspiration from it.

@yariplus ugh, I can try something this weekend, but I don't really love css, more into the scripting part I'll let you know by monday

@mj i think you can fork your theme and change the .tpl template for the users list page as you wish

@pitaj @sharonyue
should it be git checkout v1.8.x ?

@baris This means now calls with the Bearer token can also be done to normal api?

I think I can do an use case scenario:

A side permanent chat, so when you navigate the site, the chat remains there and only the content gets updated, while the chat is still available and you can still chat.

More or less like the navigation-bar / nodebb-skeleton than when you change topic/category/pages it doesn't get reloaded.

Oh, i thought you were using write-api endpoints. What you can try do is to create your own plugin that extends the write-api (there is an hook that let you do that), from which you get the uid of the user, you modify the request setting req.user and then pass everything to the searchController.search function.

So (this is not valid, but it's just to somehow show you):

in plugin.json:

{"hooks": [{"hook": "filter:plugin.write-api.routes", "method": "api"}]}

in library.js:

var plugin = {},
       searchController = require.main.require('./src/search');
plugin.api = function (data, callback) {

	var app = data.router;
	var apiMiddleware = data.apiMiddleware;
	var middleware = data.middleware;
	var errorHandler = data.errorHandler;

        app.get('/search', apiMiddleware.requireUser, function(req,res) {
            req.user = req.uid; //req.uid is given from the middleware
            searchController(req, res)
        }

callback(null, {
		router: app
	});

}

Then of course do the request to /api/v1/search instead of /api/search

@yariplus do you need help?

@Brophy What I do with my custom plugin is

git clone nodebb-plugin-my-plugin into the server user's home folder,
cd nodebb-plugin-my-plugin
npm link

then in the nodebb's root folder: npm link nodebb-plugin-my-plugin. And I never lose the plugin, if I have to release a new update I just do a git pull in the plugin (original) folder, then is updated automatically when I restart the forum.

So in your case I'd say create the nodebb-theme-your-theme folder somewhere in your server, do npm link and then in nodebb npm link nodebb-theme-your-theme .

But I think this is suggested for development environments, not for production, even if in my case is working pretty well
Another way to do it is to install your theme with npm install git+https://git@github.com/<your-git-user>/<your-private-theme-repo>.git