Minor FYI....Elasticsearch has made a strong stand that they are not a database. There are certain levels of consistency and reliability to qualify as a database that they have said they cannot support. But if your data isn't critical, and you don't mind a noticeable a delay between when you write a document and when it available for reading, then that's fine. 🙂
Usually, a single cup. Although at times one may choose to "super load" the rig and go for two pour overs sequentially. Much better to just have a second cone. 😉 And third, fourth, and so on. Then boil a group pot of water and each can "season" to taste. This approach prioritizes/optimizes for quality over quantity.
Which just aint' gonna' cut it for some people. My wife, for e.g., likes very strong coffee. And lots of it. So she uses an automatic coffee maker and needs a couple cups intravenously to jump start her mornings. Last weekend her Cuisinart automatic rig and burr grinder both bit the dust. Good riddance! Worst coffee maker ever! Hence falling back to the old tried and true #2 cone. Oh yeah, the #4 filters are used in the automatic 12 cup rig. #4's will work in a #2 cone just dandy. Long after any fancy fangled automatic drip rig sporting useless features has given up the ghost...
@macfan Not strictly true -- while you can accomplish a lot with just front-end styling, our theming engine allows you to change the underlying templates as well, so you are not limited to having elements in specific positions.
For example, if you want to have your reply buttons somewhere else on the page, or remove them altogether, you can do so by updating the topic.tpl template.
Something SQL maybe? Like mysql? I would touch nothing thats licensed on SSPL
As mentioned above, NodeBB supports PostgreSQL. A far superior RDBMS to MySQL, imho, btw.
What kind of code?
Code requisite for "porting" nodebb db backend to whatever your dream data store may be. 🙂
I, too, am none too keen on SSPL. While I am sensitive to both sides of this issue, in reality the SSPL affects me personally minimally. Meanwhile, MongoDB does a kick ass job. Hence I am electing an "If it ain't broke, don't fix it" posture.
That said, next NodeBB deployment will likely take a closer look at PostgreSQL.