aka "the One Plugin"
In the interest of making available plugins easier to find and install, I made a plugin that will do just that!
Now:

*Some console typing required

Just:
npm install nodebb-plugin-finder

(maybe even for the last time!)

Github

History:
v. up to 0.0.4: works with nodebb v. 0.3.x
0.0.5: Compatibility with NodeBB v. 0.4.1

UPDATE: this plugin is now deprecated, as the functionality has been implemented in the core product. It will still be available on github and npm for functionality up to (but not including) NodeBB v. 0.4.3

@Blue-Orange said:

NO.......just a complete redactor any ass/dummie/nono/beginner can use with all the options...

I get your frustration, but yelling at people to build your niche idea of what a perfect composer is isn't going to get you anywhere.

Quite frankly, you're asking for the world here. There's really no such thing as a "composer that has all the options that any user can use". You're basically asking for Microsoft Word as a composer, which, I'll remind you, also comes with a learning curve (a tiny percentage of users actually knows HOW to use all those features). It doesn't work, and even the ones that come close like tinyMCE have their own problems, even with the thousands of man-hours of work on it.

If you can't get you want here (which is free, by the way), contract it out or build your idea of a perfect composer yourself, instead of yelling at everyone for being an idiot and not creating your idea of a perfect composer.

So, I hope I'm not speaking too soon, but this should get you guys up and running (OSX Yosemite)

So far what I've done is:

• upgrade to node 0.12.5 (0.12.x should be sufficient)

  • I'm not sure if this is necessary. I did it because I read that there's better support for debugging clustered apps due to the way it passes the debug port to child processes, but it still wasn't working for me using most of the tutorials on the internet

• install node-inspector

• if like me you had already installed node-inspector and nodeBB prior to upgrading to node 0.12.x, you'll have to rebuild your node packages:

  • in your NodeBB root directory, run npm rebuild
  • in your node-inspector root dir, also run npm rebuild
    • I installed node-inspector through npm, (npm install -g node-inspector) so I had to go to /usr/local/lib/node_modules/node_inspector and run npm rebuild

• Start nodebb in development mode: (in NodeBB root dir): ./nodebb dev

  • this starts up only one fork so you don't get the EADDRINUSE error

• In a new terminal, run node-inspector & (spins up as a background process, so if something goes wrong, use ps aux | grep node-inspector to find the pid and kill it)

  • this will output something like

    Visit http://127.0.0.1:8080/debug?ws=127.0.0.1:8080&port=5858 to start debugging.
    

• Press enter to get back to the command line

• Type ps aux | grep app.js:

    brian           79177   0.0  0.0  2432772    660 s006  R+   10:03PM   0:00.00 grep app.js
    brian           79089   0.0  1.1  3763608 183804 s005  S+    9:41PM   0:04.91 /usr/local/Cellar/node/0.12.5/bin/node app.js
  

• the pid for NodeBB is 79089 in my case, so I just send a kill -s USR1 79089 and you should see this in the terminal where you spun up ./nodebb dev:

    Starting debugger agent.
    Debugger listening on port 5858
  

• Go load the address you got from node-inspector in your browser ^ (it might take a second to load)

• Set a breakpoint somewhere (that you know how to hit) and you should be up and running!

• Now you can also just ctrl-C to quit the nodeBB process. If you want to start it again:

  • Start ./nodebb dev again
  • Use ps aux | grep app.js to find the pid again
  • Since node-inspector is still running in the background, you just have to send a kill -s USR1 <pid> to the new pid of the running nodebb instance, and refresh the browser window that had the debugger open originally

@artesea said in Default search, Solr, importance of full-text search?:

plugin dev around here is lacking any real effort.

Please stop making comments like this.

1. The code is free and open source so you’re free to fix it.
2. You sound entitled. If you’re paying for the plugin you can complain like this.
3. The lack of effort is really on your part if you’re not willing to contribute.

Free software != free support

@tradingdojo lots of people come in with ideas for what this platform could do; you're not the first, and certainly not the last.

I think that @pichalite's (somewhat salty, imo) response is that a lot of requests come in like this, but are detrimental to the core project, either as a distraction from what the software is supposed to do, or a feature that only a few people will use.

I've been at a company where feature bloat was a cancer in the product, and was a major factor in why it was hard to implement a lot of things easily. I really respect that this team judiciously chooses to leave things out of core and build everything as a plugin (which has its own problems) but it essentially avoids the scenario where person A has to deal with all the feature bloat that they won't use because person X really needed feature Y.

However, the great thing about this business model is, it's open source and free for you to hack on, so no one will stop you from using it as a project management system. I do agree with pichalite that effort is probably better spent using something that's designed more for your purpose (trello, quip, confluence comes to mind), but it's up to you.

Don't NodeBB and Drive, @JaredBusch !

Post (hotlink) an image into the forum by just pasting a URL, way easier than downloading an image only to upload it again.

Current version on npm is 1.0.2!
If you want uploading, take a look at @barisusakli 's imgur plugin.

Git Repository

...or, run

npm install nodebb-plugin-imgbed

Updates:

• I fixed the ACP page to look less terrible
• You now have the option to choose other syntaxes to parse to (bbcode, html)
• The preview window now renders correctly.

Check this out: http://codeology.braintreepayments.com/nodebb/nodebb

It's some visualization of any code repository on GitHub

@frissdiegurke yeah I missed that "automatically" part

In my defense, I'd rather reduce the number of external dependencies, and knowing the versions compatible, could still make an installation reproducible without needing to depend on anything. Maybe I just like doing things the hard way, haha.

Still, kudos for that quick script! Wasn't trying to make it sound like wasted work.

Since this software is built in node and I'm a huge fan, I saw this come across my feed and thought it might be something you guys would want to be involved in: https://medium.com/@nodejs/nominations-open-for-node-js-foundation-individual-membership-director-4f004f5cc140#.eyhh09t3s

@xenforum said in May Docker Discussion:

I'll definitely be using nodeBB in Docker if I end up going with that.

Like this, it would make dabbling with it more approachable for less technical users (not suggesting that @xenforum is less technical), but docker-compose up is much easier than, at minimum,

• install node (from nodejs.org? nvm? apt-get? brew?)
• clone NodeBB repo
• install Mongo / redis / Postgres (again, multiple ways to do this)
• run npm install (hopefully not with sudo)
• run install script
• (maybe even) install and configure nginx.

The only thing running in docker makes more difficult is developing plugins. I can't house the plugin repo from within node_modules because for all intents and purposes, the stuff in node_modules is ephemeral, and you can't symlink from outside the NodeBB root because of the way Docker context works.

@julian said in May Docker Discussion:

Case in point https://duo.com/decipher/docker-bug-allows-root-access-to-host-file-system

Ouch...!

This article is pure FUD; it's like saying that because a car thief can open your door right after you unlock it and before you get in, all of the locks and the car alarm are useless.

From one of the paragraphs near the end:

This scenario would only be possible if the container was already compromised and a user was using 'docker cp' to replicate the container files and occurred at the same time the copy was being made, a window that is only a few milliseconds.

There were some other, more prominent articles describing root exploits by attaching the docker socket into the container, a scenario which is both unnecessary and uncommon (it would only be used if you're trying to run Docker in Docker).

So while it's not bullet proof (I mean, what technology really is?), it's more secure than installing a random package from the internet with sudo npm install

@scottalanmiller said in May Docker Discussion:

@Bri said in May Docker Discussion:

But that’s what Docker brings to the table that no one else has done (as consumer friendly) yet: containerization on the desktop.

Does it really do that? I can containerize with Snap, Flatpak, LXC, etc. on the desktop just the same, unless I am missing some feature. What does Docker do that I didn't already have?

Yes, but I'm only coming from the perspective of development experience. Admittedly, I haven't tried any of the things you mentioned, but a cursory search shows that:

• Snap doesn't work on windows yet
• flatpak appears to only work on Linux distros
• Docker is a high level abstraction of LXC, which again only works on Linux kernels

So how much work do you think it would take to get this to work on both Windows (your preferred development machine) and macOS?

You could just give a Linux VM image to devs, or make them dev on a Linux machine, but I've worked that way before (in a VM) and I hated it. Docker has by far been the most portable and reproducible solution for development work that I've experienced.

It would be easiest (and cheapest) to host both on the same machine for starting out.

@scottalanmiller has done some great scaling of this platform, he may have some pointers

@omega what is the output of this call:

cat /etc/os-release

Do you remember if you installed node or any npm packages as root (which is the user you’re running commands with when you sudo)?

What is your hosting provider?

The errors you’re getting are not typical for node installations so you need to provide more information about your environment.

As an aside I’ve had a lot of trouble with n and will probably migrate back to nvm

what OS are you running on?

@scottalanmiller said in May Docker Discussion:

@djensen47 said in May Docker Discussion:

Docker has become the defacto standard for containerization.

And Windows is the de facto standard desktop.

But that’s what Docker brings to the table that no one else has done (as consumer friendly) yet: containerization on the desktop.

For developers, this can save so much time in terms of onboarding, setting up a new machine for development, and consistency.

@MJ said in Dark mode theme yet?:

We did made a few changes in CSS

Custom CSS or custom theme?

Just curious what the architecture is behind it? Is that pure NBB + 1 beefy VPS? Varnish? cluster?