The viewer app should expose each route as a function, so that way you can host it in a serverless way, or on a traditional server. The functions for each route would then need to call our 'pub' server (the DB).
That means the sbot that gets passed in would need to be either a local sbot or a muxrpc sbot, in the case that this is hosted serverlessly. sbot in this case would function like a cloud-DB like firebase or what have you.
As a demo we are hosting the pub server and also the viewer app from the same project. They are served by the same node process.
The viewer app should expose each route as a function, so that way you can host it in a serverless way, or on a traditional server. The functions for each route would then need to call our 'pub' server (the DB).
That means the sbot that gets passed in would need to be either a local sbot or a muxrpc sbot, in the case that this is hosted serverlessly. sbot in this case would function like a cloud-DB like firebase or what have you.
As a demo we are hosting the pub server and also the viewer app from the same project. They are served by the same node process.