NodeBB Development

Lavish.

Yeah I gotcha, I know exactly what you mean. It's something we'll think about eventually (traditional documentation generated from comments within source) but moving to repo is a step in that direction I would imagine. And thanks yeah will update the link tomorrow

it can be written in teawith2sugars for all the difference it makes I prefer my tea black to be honest @psychobunny you'll not be able to discourage me through such little issues hehe

Glad to report that as of today, April 25th, all instances of our Premium Hosted platform benefit from backups stored via the Tarsnap backup service. Our previous backup solution consisted of local file system backups of each instance's database contents, persisted to the local file system. This had two shortcomings: Backups were not hosted off-site (a big no-no! ) Uploaded files in /public/uploads were not backed up I'm glad to say that both of these shortcomings have now been addressed. Luckily, we have never had to restore a NodeBB instance from back up, thanks to our reliable hosting from DigitalOcean. Hopefully, we'll never have to Interested in having us host a NodeBB for you? Check us out at http://nodebb.org!

Not sure what you're trying to do - publish topics to NodeBB from another software? Wonder if this will help you: https://github.com/psychobunny/nodebb-plugin-blog-comments Lets you post a new topic (or reply to topics) from Ghost. I want to do WP in the future as well

1、Can I get data format？ 2、websocket use port 80？ 3、Can I write a test example to send topic by websocket ?

@realZ Not entirely sure on your question, but you could try here

@psychobunny Yeah I did remember this but I forgot when it was removed or whether it was removed completely or not. Any how, thanks for creating an issue for it.

Btw: is anybody except me using this awesome build-tool? https://www.npmjs.org/package/nodebb-plugin-livereload 24 downloads in the past month shows that there are a few people using it

@Thomas-Krickl said: @trevor maybe this could be for interest: post indivual layout with {{cid}} That's what I recommended, lol and this is for something totally different that what I am asking.

Yeah, like @frissdiegurke mentioned, timeago uses separate locale files to override the "templates", but there's no way to use multiple templates based on the situation (shorthand for some, full for others, etc) without fundamental changes to timeago itself.

Hey there @rahenr, have you tried this guide?

https://github.com/julianlam/nodebb-theme-viridian Not close to ready yet

@geoffb Agreed, definitely hoping to have that in in the next version

Our upstream provider has notified us that there may be short periods of latency or packet loss associated with some preventative maintenance regarding servers in the NYC2 data center. This should not unduly affect any hosted NodeBBs, although we will be monitoring them during the affected periods for potential problems. START: 04-15-2014 20:00 EDT (UTC-4) END: 04-15-2014 23:59 EDT (UTC-4) We will be doing some preventative maintenance with our internet providers. Expected Impact: We are expecting no impact but there may be short periods (1-3 minutes) of latency or packet loss as traffic is rerouted to available providers. Approximately 30 minutes prior to starting any work, we will post and update on progress on the www.digitaloceanstatus.com website.

I believe he published it, or at least uploaded it to github... should ask him.... @trevor ?

@frissdiegurke I keep a running tally of things that break in the "Gotchas" post that I do for each minor version.

@miksago Replied to indexzero. I do recall DocPad uses peerDeps in a similar system, so perhaps we can emulate that.

@psychobunny Nah, @julian is too nice of a guy to be fired. He's yours 'till Thy Kingdom Come

Something that interested me when I first started hacking on NodeBB was how the platform uses realtime communication through socket.io (and websockets). This interest stems from work I did whilst working as a realtime engineer at Pusher several years ago. One of my research projects whilst there was to look into how websockets get used in production, and other use cases for websockets besides the standard "subscribe to a channel and receive events". In 2011, I gave a talk at Keeping It Realtime conference in portland about some of my findings, you can watch it here: http://2011.krtconf.com/videos/micheil_smith (long hair and all) or check out the slides here: https://speakerdeck.com/miksago/krtconf-websockets-sub-protocols How NodeBB currently seems to use realtime communication: RPC: Request data from the server, get a response back, present that data to the user (or send data to a server like you would POST to a HTTP server) Channels: Used for user to user chat messages Events: Used for online/offline states of users. I may have missed something here, so, let me know if I have. Most of the websocket usage appears to be in RPC style messages: Get this piece of data do something with it. At present, all realtime communication for NodeBB is built on top of Socket.io, which uses a protocol more tailored for event type packets, rather than for RPC style packets. For this, something like JSON RPC may be more appropriate. Refactoring this deep internal of NodeBB would make the platform more resource efficient on the wire, and also allow for better logging and handling of data. You'd know exactly what has failed on the client-side or server-side and be able to give an appropriate response. In the code, refactoring this level of things would make the code far cleaner, and give option to provide all HTTP Verbs over WebSocket or vica-verse (meaning if you wanted to, you could make 90% of NodeBB standard HTTP. You'd end up with an "api" module internally that is everything that can be exposed, which simple returns back standard javascript objects. For user-to-user chat messaging you could still multiplex that onto the same actual websocket / socket.io connection (although it's arguable if this is actually beneficial). Why do any of this writing or work? Interest more than anything else, but it may make the code to NodeBB cleaner, and improve maintainability.