... but possibly not in the most digestable way. In summary, here's what you need:
Redis configured in config.json so it will be used as pubsub and for storing user sessions (volatile data)
One of the workers needs isPrimary set to true in config.json, conversely, the other instances need jobsDisabled set to false
For socket.io, you will need to make sure to use a ip hashing strategy when routing requests from the load balancer. A typical round-robin style means the socket.io handshake will fail since it ends up hitting different servers.
Great, the build fininshed with ./nodebb build --series. Thanks!
I will keep this command. After that I tried again ./nodebb upgrade and monitored with top the ram an CPU usage. The build process broke with an error
Error occurred during upgrade: Error: ENOMEM: not enough memory, read
I got this error the first time. In all my other attemps no error occured.
How much ram is recommended for the usage of nodebb?
Let say, I have a site (not a NodeBB site) and it has a newsletter form where users can subscribe by filling in their names & email addresses. After they hit submit, I'd like to redirect to the the forum site (Registration page).
@julian Do you engage in a more intimate relationship with Haraka?
Niche third party platforms would be far less likely. Postfix is built into nearly all production platforms and configured out of the box for most usages (standard SMTP relay.) His point was that they don't get their hands dirty with any specific email implementation and leave that for the admins, they just send email out on whatever protocol or API is selected and the rest is up to the email admin to configure.
@mosthated , Most probably your website already in production (hope it's being doing well ). Still, if you'll need to auto-resize the NodeBB embedded in iframe into a host website, try this plugin https://www.npmjs.com/package/nodebb-plugin-iframe-resizable (together with iframe-resizer of course). I wrote it just because I have struggled with exactly the same problem as you.
@PitaJ Cool! If the query string only changes on ./nodebb build then "Cache everything" works well. I thought the query string was different for each user or represented some token/cookie. I guess I should have checked how it is generated before posting.