Pika is a persistent huge storage service , compatible with the vast majority of redis interfaces (details), including string, hash, list, zset, set and management interfaces. With the huge amount of data stored, redis may suffer for a capacity bottleneck, and pika was born for solving it. Except huge storage capacity, pika also support master-slave mode by slaveof command, including full and partial synchronization.
@Mukkamala-Akhil said in Please let us know whether NodeBB will be actively maintained as Enterprise Grade Community Software. ?:
@scottalanmiller said in Please let us know whether NodeBB will be actively maintained as Enterprise Grade Community Software. ?:
Not rude, just wondering why you were tagging me for input for plugin requests. I'm a pretty random person to have asked to respond about them.
Cos, You replied to my previous thread. So I thought you'll be throwing some light about NodeBB.
Sure, but your questions were about feature requests. Your original question was about when NodeBB would be enterprise maintained, and that was easy to answer... five years ago and continuously since then. It's absolutely enterprise ready now.
Your next set of questions weren't really questions, but just mentions of features specific for you that you'd like someone to develop. There wasn't really a question to answer there, it's just a note that you'd like to see those features. Not much that I, as a long time user, can say about those.
I can shed light on the usual paths... you can make a thread requesting them (one thread each or no one will notice), but unless they get loads of traction, there is no reason to assume that NodeBB will even consider that - that's not how the core system works. You can hope that others want them too and that someone third party makes a plugin for you to use, but if that is going to happen it is most likely to have already happened. You can offer a bounty on the plugins. Or you can hire either NodeBB themselves or a third party to make plugins. That's easy to do, but expensive.
Other than that, I'm just an end user like you, but not one that wants those features so am glad that NodeBB is not focusing on them.
The reason that no one responded to that particular post is because, if you read it, there isn't a question - nothing that would warrant a response. So I had read it, but it just seemed like you were mentioning a wish list. Which would make no sense for me to respond to since you weren't wishing it from me.
@PitaJ said in Scheduled Posts:
It may also be possible to set up a script running client-side that would submit a post at a certain time, though that would require you keep your tab open (but would probably be better than the CLI method).
Making a little app that does it externally would only be so hard, too.
@Enrique the main problem you seem to be having is that you are not aware that there is a frontend and a backend to NodeBB. You have to wire up the controls from the ACP and make a call to the backend (via websocket, for example), and then you can call server side libraries.
Thank you for your reply, and sorry for lack of information.
http://22.214.171.124:4567/nodebb/ → success to show nodebb.
http://126.96.36.199/nodebb/ → return 404 on parent site(my case is wordpress on nginx).
http://188.8.131.52:4567/ → return misconfigured csrf error on nodebb.
http://184.108.40.206:4567/nodebb → return /nodebbcategories not found on nodebb.
I reloaded nginx.
I setup and restart nodebb each time.
nginx -t → syntax and test is successful.
now I am trying below
I've been noticing some UI issues every time a user logs in or out.
Basically right after you log in, some of the styles do not get picked up (i.e. logo becomes larger, recent-topic cards stop displaying content). Refreshing the page fixes the issue but this is not ideal.