General Discussion

@a_5mith Thanks!!

Thank you for your support

how to set logged in user programatically?

@Ted I love that subdomain What would the forum be, http://criticisms.tedrinehart.me?

@Ted does it?

Seems like it could be interesting for those that want Cloudflare with Websockets, but without the price. http://blog.coinkite.com/post/109233166001/cloudfire-open-source-replacement-for-cloudflare Excerpt: CloudFIRE is a full stack for delivering web apps. It uses NGINX as the web server, and extends it with lots of custom Lua code. The Lua code runs inside the memory of the Nginx workers, and provides the following services: •Fake browser detection and blocking •Basic session cookies •Websocket fan-out / message passing •Content cache from redis and/or disk •Generalized virtual hosting: a single IP can host many domains •Technologies: Nginx, Lua, Redis, OpenResty, Websockets, FastCGI, Python, Flask, FreeBSD. It can serve static content directly, dynamic content via FastCGI, and also serve cached content from Redis. Learn more at CloudFIRE on Github

Thank you for your note, @julian I acctually found what I were need. Adding an appropriate string to config.json - solved my problem. "socket.io": { "address": "http://myforum.com:8000" } Thus websocket will use port 8000 on establishing the connection. One of openshift's bottleneck, that held me up. Done

As @pitaj mentions, invoking sudo with NodeBB is bound to bring you trouble -- no need for superuser privileges for NodeBB, and I'm thinking of having NodeBB run as the nobody user, if possible...

We just removed it from the ACP, it can be put in config.json now in a socket.io block. https://docs.nodebb.org/en/latest/configuring/config.html

I did Restart of my Nodebb Forum and now don't work the Panel of Admin. WTF? I have this Plugins : http://i.gyazo.com/1b437a3267beaf5db0385e572cd6239c.png O.S : Windows Server 2012 Nodebb Version : 0.6.0

I had the same issue with the latest version of everything. I gave up and reinstalled and it works now. https://community.nodebb.org/topic/1669/spam-be-gone-plugin/63

@pitaj said: @Master-Antonio add your domain in the config.json file which sits in the NodeBB main directory. Did, but don't work.

While browsing the 'net, I found a neat little IETF draft standard called JWT (JSON Web Tokens). Basically, the idea is that instead of having sessions on the server and a cookie to match a HTTP request to one of those sessions, one or more claims (i.e. user ID or admin status) are stored in a JSON object which is then signed by the server. (currently through either HMAC, RSA or ECDSA) The client then stores this in usually either localStorage or sessionStorage and sends it along in an HTTP header with any request requiring authorization. For example: client logs in with username "Example" and password "password" server if user and password match, issue a JWT containing the payload { 'userId': 47 } and send it to the client client stores the JWT in sessionStorage (later) client creates a new topic and sends the JWT along in the Authorization HTTP header server validates the signature in the JWT from the Authorization header with their own secret/key and if it's OK, uses the data from the JWT in the processing of the request (in this case, the userID of 47 is used as creator of the topic) Pros of JWT: The server doesn't need to store sessions! => less load on the server & no shared session store is needed when scaling horizontally as long as all instances share a secret or public/private keypair No cookies => no CSRF! Cons: XSS becomes more dangerous - any malicious script with access to the client's localStorage or sessionStorage for a site can fully impersonate the user until the token expires or is deletes There might be more cons & pros, I am neither good nor experienced enough to fully understand everything ("everything" is a lot though, I do have trouble with way less than that anyway, don't take my words for granted, do your own research, etc. etc. you know the drill ) Some links: General introduction: http://angular-tips.com/blog/2014/05/json-web-tokens-introduction/ Slightly more detailed introduction with INFOGRAPHICS(ish): https://auth0.com/blog/2014/01/07/angularjs-authentication-with-cookies-vs-token/ Web-based token decoder: http://jwt.io/ Express middleware: https://www.npmjs.com/package/express-jwt

hi, is there any static nodebb api that create post?

@a_5mith said: Think they're arranged by last post By default. They probably should just stick in the order they're stuck though. Feature request maybe. I think it needs to be changed by admin on settings.

@Mega as @Schamper said, I only discovered this last week, so we use require.parent.parent/etc for everything, but require.main works just as well. Keep in mind require.main's "scope" is app.js, so you'd have to do require.main.require('./src/groups.js'); if you want access to the groups lib. require.main will always be app.js for plugins, since plugins are only called by NodeBB.

@birch said: I had installed using the Installing NodeBB for Dummies. ... the whole thing is a huge learning curve for me It's perfectly fine to be learning as you go. It's one of the best ways to pick up experience, and interact with content to learn exactly what things do. It appears as if you're using an outdated guide on @psychobunny's blog. While it is designed for installing at Digital Ocean, it was written for an old version of the platform, and it only installs using Ubuntu. f you're setting up an Ubuntu droplet, I must insist that you ignore everything written in the NodeBB for Dummies guide, and take a look at the specific installation instructions for installing NodeBB on Ubuntu. While the guide does an excellent job of going in-depth, the OS-specific installation instructions are what you'll need to set up a new forum/droplet. With that being said, there's a few tips for working with NodeBB as a beginner. When installing plugins or using npm from the command-line, you will lines that begin with WARN, as you have already noticed. These are usually harmless, and can often be ignored. However as you've since discovered when something says ERROR you've got a problem It looks like you've gotten some misinformation from your friend. There's no need to install PM2, or forever. Previously, there was a need as the NodeBB loader wouldn't restart the software if it went offline. With the recent versions (0.5.x or 0.6.x, I can't remember) NodeBB has the ability to restart itself when necessary. However, this doesn't mean it will detect an issue and attempt to correct it, it simply restarts NodeBB and the forum comes back up - unless there's a configuration error which prevents a component from functioning. It appears as if you've encountered this already. When starting NodeBB, there's a few commands you can use. ./nodebb start Starts your forum in "production". If you go down, it'll restart itself. ./nodebb stop If NodeBB is running, this takes your forum offline. ./nodebb log This can only be ran after ./nodebb start. This shows what's going on in your terminal. ./nodebb dev Starts NodeBB in "development". This basically combines ./nodebb start and ./nodebb log. The forum only stays online as long as the dev command is operational. If you hit ctrl+c to end the console output, you also power off the forum. This is great for doing a quick test, and seeing what happens as you make changes. ./nodebb restart Restarts your forum. Pretty explanatory ./nodebb reset has a few uses. ./nodebb reset plugins Resets all plugins to their default settings ./nodebb reset plugin="nodebb-plugin-brokenplugin" Resets a single plguin to it's default setting ./nodebb reset widgets Resets widgets. Items are moved to the draft zone. (Not deleted, just disabled) ./nodebb reset themes Resets themes. Undoes alterations (I think - could be wrong on this) and reverts it to the original items. ./nodebb reset all Resets all of the above. Now that you're familiar with these commands, working with NodeBB in the command-line should be a little simpler. In order to work with NodeBB using these commands, you will have to have navigated to the folder where you installed NodeBB. I've noticed that you're trying to use a password with redis, but there's not a redis password required. In order to use a redis password, you need to edit your redis configuration to requirepass. You could do this through the terminal, but if you're new to working with a VPS I'd just recommend downloading the config through SFTP, editing it, reuploading it to overwrite the original file, and then restarting the redis-server service. Let's have a quick chat about installing plugins. Since you're new to NodeBB, until we can get you up and running for at least one week straight, I'm going to have to ask that you do not install a plugin using npm install nodebb-plugin-pluginname or npm i nodebb-plugin-pluginname You can install NodeBB plugins (and edit their configuration) in the Admin panel. So for now, you've got an issue with nodebb-plugin-emailer-mandrill As stated, you need to run ./nodebb reset nodebb-plugin-emailer-mandrilland then ./nodebb start If you want to start fresh, I'm working on a blog post that's updated and may be able to help.