@TaLoche

It works. You helped me so much thanks!

@TaLoche said in add gif emoticons:

@NoduleJS yes in your settings by default on nodebb the max limit for a file is 2048 Ko

weird thing is that gif emoji are very small. There is a way to change their default size?

i mean that when i try to upload a gif i receive an error message (simple file upload error message).

P.S: but ok, now it work, i think i was trying to upload a too big gif (4MB).

Thanks for help me

@TaLoche it wont work. It work only with images but not with gifs. I think also that is useful an option to use external hosted images/gif. At moment i must upload them on my server

Is possible to add a list of default gifs as emoticons? I see that xenforo forums have a list of gifs on the emoji section

@fgallese yes thank you. i saw it yesterday. I lost a lot of time for that little detail. Digital ocean console uses another character set

For me is good without docker. but i really dont understand why mongodb-org dont work. if i install mongodb all work fine but for the version 4.x i have to use mongodb-org

solutions?

Seems all works fine without errors until i have to install mongodb-org. i followed nodebb docs and also official mongodb docs. it dont work on digital ocean. in local host it works fine.

maybe the error is after

sudo apt-get update

?

Thanks guys. i think i simply start with a 5$ droplet and i increase resource when needed. Then i will see in future for horizontal scaling.

I just dont understand why i cant install mongodb 4.X on the droplet. I follow the official nodebb docs and i've tried also mongodb docs but i always receive this error

E: Unable to locate package mongodb-org

Hello. I have never hosted a forum. I'm confused about what the best way to start is.
I would like to start on DigitalOcean. I'll start by using the last release of nodebb with mongodb database. What do you think is the best option?

1. $ 5 Droplet where I install server + database. I will increase resources when needed.
2. one $ 5 droplet for the database and one for the server. I will increase resources when needed.

I also need to install nginx? in localhost I never used it. My idea is to start in the most minimal way possible. any advice?

I see also droplets can be resized in resources or i can add more of them. What is the best solution?

@julian
Thanks. Yes it works fine. Only one problem.

Seems like

'action:ajaxify.dataLoaded'

is not called when i refresh the page. It is called only if browse the forum. I noticed it now because i use this hook to capture user counters and put them into the stats page.
It wont work also with simple code, outside or inside the document-ready function.

P.S: i just solved using directly

ajaxify.data

global variable. It is just a problem of the hook

I wonder if there is a filter to add custom field stats on a user profile.
ex: followers, following, my custom counter, my custom counter

at moment, i call this filter to add my counters

filter:user.account

But in this way i have to add custom css code on the client side. There is a way to add them graphically on the server side?

For example when i call this filter

filter:user.profileMenu

is not neccessary to add client css code because this function do anything

plugin.getProfileMenu = function(data, callback) {
  data.links.push({
    title: '[[pages:user/myprop]]',
    id: 'mybutton',
    route: 'mybutton',
    name: 'mybutton',
    visibility: {
      self: true,
      other: true,
      moderator: true,
      globalMod: true,
      admin: true,
    },
  });

  callback(null, data);
}

congrats for the audit scores.

First two are from my browser

Mobile Device

Desktop

from
https://developers.google.com/speed/pagespeed/insights/?url=https%3A%2F%2Fcommunity.nodebb.org&tab=mobile

Mobile Device

Desktop

From last site desktop is better than mobile than from browser.

I did a bit better performance with a simple vuejs forum, but very good performance for a complex forum like this.

from last checks

desktop: First Contentful Paint: 0,5 s
mobile: First Contentful Paint : 1,8 s

@baris yeah it's true, but you can use transaction on a multicluster with only one node, also if with a lot of limitations.
About your command example is a good idea also if it would work only with redis and postgre, with mongodb can be used like a normal batch.

I took a look to postgreSQL module, seems it support transactions, mongodb emulate the same thing with non ACID batch. I prefer to avoid SQL databases but the way data is organized seem more suitable to a relational DB

Hello. I wonder if nodebb structure does not favor data inconsistency

What i see in user/create.js file

Different waterfall and parallel async calls, but why not use a single batch request directly to the database?
Anything can happen during the execution of a function. If the server crash before the end of a function we will have data inconsistency, with incremented counters and inexistent new users or similar things.

p.s: With MongoDB 4.0 is possible to execute ACID transactions. Postgre SQL can do the same, i have no idea about redis DB.

I'm using several groups that gradually guarantee more and more privileges. Each group is reached after a certain number of posts.
They are groups in which you are automatically added or removed by the system, you cannot choose to accept or reject.
The problem is that at the moment there is no way to prevent a user from leave a group.
I wanted to use the hook

'action: group.leave'

and then re-add the user after its call, but this solution could create a circularity that I don't like.

example: If an admin wants to delete a user from the group, he could not do it, because this hook does not provide information on who was doing the action, then it continues to re-add a user despite any privilege.

I think there is to use the same solution used for registrations, under the check mark
"disable join request" can be good to have "disable leave request"

@baris
i will do it! thanks you

If someone is interested at moment there is a ugly way to avoid a delete.

you can add your logic here

'action:topic.delete'

restore the topic if the caller is not the admin and the topic is part of a specific category