It now behaves like it just doesn't execute firePiwik(data); in the "$(window)" area. This is all so strange.
Not much to learn from my experience, since my #users/day is pathetic.
As for tdwtf, I personally don't believe it would have been faster with Mongo, but I could be wrong. I looked but unfortunately I could not find the exact benchmark chart I was referring to earlier. Nevertheless, see here: https://what.thedailywtf.com/topic/25362/so-about-that-postgresql-thing/8?lang=en-US&page=1
Finally, you should consider visiting tdwtf often, the posts there are among the funniest I have ever encountered
It's possible, but not easy. There are a few options:
create a theme for NodeBB, render NodeBB in an iframe and embed that in your page
render NodeBB templates in an angular component and embed that in your page
interface directly with the NodeBB rest API, creating a frontend in angular
@julian Cool thanks, yea poor ns-embed is not happy in 1.12.2 - I and others already flagged in that thread, still, A Great plugin!
Ok SMTP/EMAIL is fixed!
Some deeper DNS/MX work seems to have made the difference and using "encrypted" setting - initially I was using StartTLS as per email provider SMTP guide, which specified TLS - tested it again and StartTLS broke it.
It's a little difficult to explain, but at a high level, we're a single page app, which means when you click on an anchor, we request the JSON for the new page, render the html on the user browser, empty everything in #content, and inject it into #content. The overlay is a transition that makes this process a little smoother.
We use a templating engine called Benchpress to render templates on both server and client-side.
Not a NodeBB specific test, but a NodeJS one, and just an isolated example, but suggests that Node at least is far faster on Linux. Now keep in mind this is old so pretty much worthless as a test. I'm interested to do some real testing, though.
Node.js Performance Benchmark on Windows vs. Linux at josephbill.com
@julian said in Cannot start nodebb with systemd:
Hi julian, sorry for my delay response.
I changed the services as you suggested, essentially this was my first implementation.
I removed the file output.log, then I rebooted the system and started the services, when I went in the logs folder the file output.log was empty.
I used journalctl -fu nodebb.service to see the log of the service, and I discovered a nice thing:
UPDATE 2 [FIXED]
Okay, so after spending some times on this, I discovered what is the cause of the problem. Essentially, I have installed nodebb as root account (which is wrong, my bad), and the systemd service was configured to run nodebb as the user "sfarzoso", but that user was not the owner of nodebb folder, so when I started the service using systemd, a permission problem happen.
For fix this, I chowned the "opt" folder for "sfarzoso", which is the folder that I need to install nodebb, then I cloned the repo of nodebb and launched the setup again.
All works now.
Thanks for the attention, king regards.
@PitaJ said in email notifications for post queue:
Just so everyone knows, there's a search bar in the ACP, that searches the ACP. If you're looking for a setting that may be a good place to start.
Oh, I've never seen that. It's in all that "Dead space" way up top that I scroll past before it even loads because there is so much wasted space. Good to know that that is there.
Would be nice to see that area compressed a bit, so much empty space up there.
@PitaJ said in "csrf-invalid":
@PatheticMustan please try removing the config.json socket.io option. It's dangerous. More information here: https://community.nodebb.org/topic/13388/faq-websockets-not-working-due-to-misconfigured-origins
Thanks for the tip! I have since removed it, and it still works
@PitaJ said in Private Git for install plugins:
@Joykiller there's no easy way to keep the links with npm, but yarn is better at not killing them.
Ah ok, well ill put up with it. Till I write some bash that checks to make sure the links there or something and if not replaces it after some trigger. I'll look into it later.