rns.recipes

It's time for me to fight my fear of being called a n00b and start asking questions :)

How do you run 2 or 3 or more instances of Nomadnet simultaneously for the purpose of:

a) have 3 sites about 3 entirely different domains

b) or having a dev, staging and live environment. I know there's a way to stop it from announcing, but in my opinion 'dev' shouldn't accept connections outside loopback, period.

I was told I could use proxmox, but I see meshchat X allows to spool infinity instances, although I did not test it (I have my reasons to want to use nomadnet on my permanent, transport + propagation node).

Thank you. I have to admit I find the idea of not having ports both liberating and confusing :)

You can run multiple instances of rns by using multiple config directories. I use this to run multiple isolated networks on the same server. I also have one instance (with enable_transport = False) that connects to all the isolated networks. This instance runs my nomadnet pages. All the isolated networks can reach the nomadnet pages without the networks connecting to eachother.

Run rnsd with alternative config:

rnsd --config /home/user/.reticulum_second_instance

And change the name of that instance in the config file:

instance_name = reticulum_second_instance

You can check the instances with rnstatus by pointing to the correct config directory:

rnstatus --config /home/user/.reticulum_second_instance

You can now run a nomadnet instance on every single rns instance. Just point nomadnet to its own config directory.

Bit of a fragmented reply, sorry for that...

Run a second nomadnet instance on a second rns instance:

nomadnet --config /home/user/.nomadnet_dev --rnsconfig /home/user/.reticulum_second_instance -d

Hope this helps.

Came here to answer, but you gave it already Mees :)

ahhh! thank you mees (love your page by the way). so the trick is, to run multiple rnsd with one nomadnet on each! Make sense now! Cheers!

You can also just run three (or 15) different nomadnet instances all connected to the same RNS instance. It's intentionally made very flexible, so you can make any kind of setup you might require. In that case, just run one RNS instance, and only specify different --config paths for the nomadnet instances. They'll all use the same RNS instance, but be completely separate otherwise.

Personally, what I'd do in your situation (unless you need some sort of extra isolation for security purposes or such) is to just run one shared RNS instance, and start as many separate nomadnet instances as you need. All of this works "out of the box" with the default RNS config.

The first RNS-based program you launch (in this case probably rnsd) will set up a shared instance. Any other program you launch afterwards (in this case, your nomadnet instances, Sideband, MeshChatX, and so on) will automatically detect and use this shared instance. It all happens automatically.

Thank you!

ivan has made rns-page-node for this purpose
i (guess what, its self promo time) shat out nomad-pages for this purpose(DO NOT USE IN PRODUCTION, IT SUCKS VERY MUCH)
although if you want to use nomadnet, you'd need to do nomadnet -d --config .nomadnetwork/someotherconfigfile
although i prefer -dc(no ui, log to tty)