@aokp Fact that sth is actively developed doesn't mean said development is going in right direction......
And (tbh) looking into repo's commit history I can see that there is more than one active directions..... in other words - it seems that each & every dev with push right has its own strategy how NodeBB shoul develop......

Slowly it starts to be as in proverb: if something is for everything, it is for nothing..... sad as NodeBB has enormous potential waiting to be unveiled.

Points why NodeBB is where it is::

• Main admin/inventor @julian is simply clueless as to what to do next,
• NodeBB has stupid CLA.
• JavaScript,
• some stupid DB chosen - why not mysql?

And muchb more....

@julian and this is enough. Im done with any type of conversation with you.
In addition to this :: I will not contribute any of my asset (time/code/whatever you think I have) to NodeBB.

@bri said in ./nodebb setup Permission denied:

@wojciech-lisik said in ./nodebb setup Permission denied:

I really have indepth knowledge of how public-facing server should be architectured.

You obviously don’t. And now I fear for the customers of those 1k+ servers you’ve set up.

You don’t happen to work for Equifax, do you?

No, I dont work for Equifax.... I work for completely different company.
Nothing to fear about, trust me

@bri said in ./nodebb setup Permission denied:

@julian Honestly, I wouldn't chmod, just delete and reinstall (or move) in a more appropriate location, and then adjust permissions (if still necessary).

@Wojciech-Lisik You shouldn't install programs in /usr/, but rather something more like /usr/local/opt/ or, ideally, some subdirectory under your user's home directory (for development). If you're setting up a production server, you'd want to create some directory structure under /etc/ owned by a special, non-root user with the least privilege possible. Most of my setups follow the paradigm of storing server files hosted by NGINX under /usr/share/nginx/ and setting rwx privileges to the special user I set up only in that folder.

You should never have to use sudo or the root login to install nodebb (or any other web software, for that matter), and doing so can be a huge security risk.

Here's a neat Superuser answer that outlines what the intended usage of each folder in a *nix machine is for.

Nice write but really dont even try to teach me how things should be done in IT. I have setup 1k+ servers in my career and I really have indepth knowledge of how public-facing server should be architectured.

@julian @PitaJ and other wise-heads :: how installer is supposed to write sth to folder which access to is limited by permissions? The only way is to use sudo and change ownership of installed file/s aftewards.

JS sucks

JS is commonly used by crackers so its not trustworthy language.

Installer puts *.js into /usr/ and ls -alh /usr gives root:root as an owner, so......

@pitaj if thats the case, than how on Earth installer is going to modify system files?

try with sudo like sudo ./nodebb setup

Sorry guys, but very first thing I did after I bought my Win10 laptop was to remove Edge and install Chrome.
If you want to get your computer infected, than stick with Edge.

In nodebb:

Admin > Location & APIs > SSO > Twitter > Add new api token.

In Twitter:

(User menu > Settings > API > generate SSO.

Hey, Ive got the same issue. We should inform plugin author of this.
For now I disabled it. Waiting impatiently for an answer.