Running NodeBB on multiple VMs?
-
I just set up a NodeBB server over at fly.io, and everything was up and running remarkably fast. The only problem is that, by default, I am making use of two fly machines to run the app (the only configuration needed to get NodeBB working was scaling the machines' memory up to 512mb).
The problem is that the VMs are not sharing the node app correctly. It's as if each machine has its own instance of NodeBB. For example, if my request is handled by machine 1 then I am taken to the live forum, but if my request is handled by machine 2 then I am taken back to the NodeBB installation page.
Is it possible to run a NodeBB app between two virtual machines? Or do I need to reconfigure for one?
-
-
@o-o - I was not able to make fly.io work. Unfortunately I don't remember all the details, but effectively fly.io and NodeBB were working under different assumptions as far as local resources were concerned. Upon idle my fly machine would lose track of the fly database, and upon restart it would attempt to restart NodeBB from scratch. Until the idle everything worked fine. But at the end of the day my issue was automatically serving the precompiled Javascript resources that NodeBB presupposes.
Outsourcing the database to something like S3 might fix the problem. Also, fly.io changes very quickly, and I know others were having the same problems with other frameworks, so they may now have a workaround.
