RNS Logo

rns.recipes

◈ 9ce92808be498e9e05590ff27cbfdfe4

App ecosystem planning

Question Help

Started by Blastertoad ·

edited #1

I think I understand the basics of rns and setting up nodes, messaging with sideband / meshchat etc.

 

What i am currently struggling on as I plan projects around rns is planning how multiple clients or apps are to coexist on a system. Let's for instance consider breaking nomad net out to a dedicated browser. Now if a user downloads NomadBrowser, is it going to look for rns running, is rns packaged with it like meshchat so running browser is an rns instance. Or should it be a dependency to download an rns deamon.

 

When we have browsers, rngit, games, etc. built utilizing rns what is the desired or recommended method here of connecting to or packaging rns. I thinks its a little wasteful for everything to be an instance of rns and need configuring.

 

Then if you are running a dockerized node, how are apps supposed to use this. Does a game server docker need an rns instance to connect to the node docker? Or a partyline server docker etc.

burger ace748e1c4e3fd4e...
edited #2

Shared instances

Post a Reply

Supports Markdown: **bold**, *italic*, `code`, ```code blocks```, [links](url)

Log in to upload images

Quote
Copied to clipboard