Posts made by julian

I'd recommend the MailChimp plugin to add users to an existing MailChimp list, then use that to send emails to users.

The error suggests a 404 page may be getting served, try going to that url, what do you see?

Perhaps you need to rebuild NodeBB?

Does Apollo have to be injected as a middleware? What app is, when passed to plugins, is not actually the express app, but a Router instance.

That might be the crux of your problem, but I am not 100% sure.

@gotwf too many variables to know for sure. They could be like us and host NodeBB on a potato server

However, we don't get nearly as much traffic as mangolassi or tdwtf

Sometimes I feel like we're a little behind with our approach to developing NodeBB (that is, not treating Docker like a first-class citizen)...

Now there's kubernetes What's next?

Correct, if all traffic goes to the WordPress site, then WordPress essentially owns the site, except if you have a reverse proxy intercepting traffic as it comes in, and deciding where it needs to go.

One such reverse proxy is nginx... Or apache... Or lighttpd

Think of it as such:

• The request for thesite.com comes in
• Nginx resolved this as a request that should go to WordPress, and thus kicks off the requisite php-fpm (or whatnot) processes to handle the request.

Vs

• A request for thesite.com/forum comes in
• There is a rule saying anything that starts with /forum is actually NodeBB
• Nginx proxies the request to NodeBB to handle

What is important to note is that how you configure nginx affects the routes on instances behind it. For example, if you configure nginx to serve NodeBB when /forum is accessed, then any /forum routes served by WordPress are inaccessible.

Hope that helps explain it a bit!

Docker discussion forked

node app --upgrade should also work to run the upgrade scripts. Give that a shot...

It looks like the version of NodeBB you're migrating to is too new. In the new installation, you'll want to git checkout to v1.7.2, and then try to start NodeBB again.

When you're ready to upgrade to the newest version, git fetch && git reset --hard origin/master and ./nodebb upgrade

Actually, it was a backend issue we update the forum fairly often, but not always for smaller issues like this one.

I'll try to update it again today

Continue, I can fork if need be.

Version 1 of NodeBB hosting was built using lxc. Worked quite well, although we didn't quite have the domain knowledge to do it well. We ended up reengineering it later on down the line.

WRT containerization, I honestly really do get the appeal. You can pretend it's all about making your dev environment mimic production, etc... but it all boils down to that "new server feeling", every single time you deploy a container.

Sysadmins used to brag about their uptime records... now it's a soft sign that you might not be keeping up with the latest security patches

Is it worth the overhead? That's up to you... I like tinkering with my servers, personally. Pretty soon it'll be a lost art.

That's awesome @baris I'm assuming backwards compatible with the old method, though that ought to be deprecated?

No knocking the guy when good content presents itself. He's the reason I have dual monitors (not three though), and have a USB drive on my keyring.

That said, the USB drive came from China (hooray Amazon FBA!) and doesn't actually work, but that's a story for another day.

He might also be a major reason I use a mechanical keyboard

@gotwf said in Which is better NodeBB or Discourse?:

I was kind of surprised Discourse became so popular, but I guess that's one thing fame will help you with.

I used to read Jeff Atwood's blog, I really liked it back then, and he said a lot of things I agreed (and still do, sometimes) with. He has a huge following and that's what allows him to speak his mind and be heavily opinionated, because lots of people will listen and change their minds. That same audience lends Discourse a whole heap of validity simply because of the name recognition factor, and all the power to them, really! I wish I had that kind of marketing clout, but here at NodeBB, we need to focus on building a superior product instead

We don't really want to have a say in whether one product is better than another. We've stolen good ideas from Discourse and Flarum, and vice versa. It all makes for a better product anyway, doesn't it?

FWIW if I tried to be as opinionated as Mr. Atwood, I'd get flamed incessantly. My average reputation on my HackerNews posts is... 1

We built our DO image on Ubuntu 18.04 with some sane configs and such. There are areas to improve so hopefully as more people use the one-click image, then we'll find out pain points and address.

That said, the image isn't live yet. It's still being verified by the DO crew

Right. Performance could be relative to resource utilisation, however. I know TDWTF had huge troubles with web scraper bots hammering the server to crawl their new content. They even blacklisted a number of user agents for that reason.

Might be the db, or might just be lots of bots crawling the site at any given time

@gotwf said in Mongodb or PostgreSQL? Ah, that is the question...:

Hopefully the daily wtf notice this thread and weighs in w/their $0.02. Pretty please?

@Ben-Lubar from TDWTF built the pgSQL adaptor that NodeBB uses, actually. They're on postgres at the moment.