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

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

@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.

@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

If anyone comes across this topic again, I've created my own version of the systemd service file for NodeBB. It's really nice to have especially in scenarios where your VPS gets shut down for whatever reason; all you have to do is start the VM back up.

https://gist.github.com/bdharrington7/2599927d41d30f11900f2099b8d8fc64

@apple-pro wow man, talk about a rage quit.

You literally started posting four days ago. That is not nearly enough time to get any meaningful help.

Software development and support can be slow (unless you’re paying for it). It’s a fact of life.

Admittedly, the learning curve is on the high side compared to other software, but no one got better at life by doing only the easy things. That’s how you learn.

The tutorials are not hard to follow, but there is some basic developer knowledge you’d need to know, all of which is very easy to Google.

Hope you fare better in future endeavors

It's a thing!

https://opensourcefriday.com

Yeah, might be more trouble than it's worth.. @scottalanmiller and @exodo have some experience running at scale, so they'd be good reference point for the kind of scale you're looking at

Hey @WildPointer, are you updating this right in your production instance or are you using a dev instance to test it first?

I don't have anything in production yet, but I've been staying on master. In regards to your conflicts though, that happens if I (or some other process) added or modified something in the directory tree.

A git checkout should be sufficient, but then you'd have to make a backup of your db and then call ./nodebb upgrade to update your db to the new schema if needed

I just tried to reproduce what you're trying to do, so here's what I did:

git checkout tags/v0.6.0
... boot up, add some groups, users, and posts, shut down ...
git checkout tags/v0.7.0
./nodebb upgrade
^ at this point, there was a db schema conflict and I couldn't upgrade, so I did:
git checkout tags/v0.6.1
./nodebb upgrade
.. boot up and check everything is fine ...
then, I could do
git checkout tags/v0.7.0
./nodebb upgrade
... boot up and verify upgrade.

just make sure you have backups! It's not version 1.0.0 yet so be vigilant about those things. I know I'm not as good at that as I should be

This plugin's admin panel has been broken for a while but I just fixed it this weekend along with some other improvements current version is now 0.2.0. Cheers!

It brings a post to the admin's attention in case it's spam, racist, or against the site TOS, etc.

Try not to shut redis down that way. The way redis works is by storing things in memory, and only persisting to disk once in a while (which is why it's so fast). Because of that, you can actually lose data if you shut down the redis server unexpectedly before it has a chance to write to disk.

You can prevent accidentally closing the tab in the future by running it as a service, or in the background by entering the following command:
redis-server&

This will run the server in the background. You can ensure that everything is saved to disk by using the command
redis-cli save

You can take a look at that nodebb-plugin-imgbed one, that's a pretty good example of saving settings too...

/shameless plug

I'm Brian. I guess compared to most of you guys I'm a bit of a lurker

I've just relocated to San Francisco from San Diego working as a developer for an enterprise community software company called Lithium. Kinda followed my girlfriend up here but I have family and friends up here too that I'm reconnecting with.

I've been in California my whole life but after graduating in '12 from UCSD (comp sci) I went travelling in Europe and Asia. I used to go to Mexico a few times a year in San Diego and I've even been to Canada! I went to Victoria though so not much experience in Canada... Yet.

I love making music and if it paid more that's what I would actually be doing, but a close second is programming and webby stuff. I've been online since around 96 when I was in middle school, putting up pages in angelfire and geocities, using cutting edge technologies like frames! I even started dabbling a little in JavaScript to make a fancy navigation bar. Little did I know how big this language was going to be...

I stopped doing that for a while though to meander off into studying music and biotech in community college, where I earned a degree in biotechnology production and a certification to be a bio technician, which I abandoned right after earning it :D. It did come to my aid, because that degree got me a job at Diageo in wine country for their wines division which was awesome. I started building computerized systems for them (as a technician, which was waaaay outside my job description), so I knew I should study computer science.

So yeah now I'm just getting settled (back) into the Bay Area, which is completely different from when I left... In a good way