I believe it should work with Discourse:
Thanks for the links. I took a look at the whole conversation and for a novice like myself, a lot of what’s being discussed is new to me, but I guess I will have to do some research and test it myself. If anything, I can always go back to Digital Ocean, right?
Contabo seems to be indeed a good option in terms of price and what it offers. I still need to understand the issue with some providers blocking email providers, which I have no clue what that is. I remember having an issue with Brevo and had to use a different port from the one recommended in the official installation. With a little bit of research and tests, anything is possible.
i think some people were confused between Inbound and Outbound.
even Ionos Telephone Support really wanted to assume i meant outbound, even though i meant inbound
Certainly looks like a shortage of virtual memory, which means adding swap should solve it.
But see also
I never quite gave myself the time to do the controlled experiments, but I very much believe that once you’ve set overcommit you will need less swap.
I would say i’ve always been impressed with the performance consistency and network download performance of Ionos VPSs for my situation, but then that depends on the exact location of your user base,
if i lived far South in the UK, Contabo would become a more valid option, however they like their Shared Networking Infrastructure - often the cause of unpredictable ping/latency.
Can I recommend all the chat about hosting providers be moved to Recommended Hosting Providers for Self Hosters?
For what it’s worth the latest update today (v3.5.0.beta8 +93) completed fine from the UI (like completely no issues not “says failed but actually worked”).
I have 2GB RAM and 3GB swap which is more than is suggested in any of the guides. We’ll see if it keep working or not, but multiple previous updates have failed
Resource requirements are now significantly lower, thanks to Introducing pre-compiled JS assets for self-hosters
So hopefully these kind of Command was killed with SIGKILL (Forced termination): ember build
errors should be a thing of the past
there’s nothing self hosters with plenty of RAM need to do for this change, if they’re using the standard install ?
No changes are required. More info is in the announcement topic.
One more reason why I love Discourse and this community. Y’all stay true to the name and engage in regular discourse with just about every post on here at some point. Can’t wait to try out the improvements and so glad I was able to bring this topic to discussion that brought the improvements.