The procedure described in How to run a local test network is also applicable for a global private network with some adaptations:
choose a port number and set the “tcp_acceptor_port” parameter of “safe_vault.crust.config” file with this value.
select the list of vaults users will connect to. Then set the corresponding list in of ip address + port number pairs in “hard_coded_contacts” parameter of both “SAFE Browser.crust.config” file (for the browser on clients) and “safe_vault.crust.config” file (for the vaults).
choose a network name and set this name to “network_name” parameter of both “SAFE Browser.crust.config” file and “safe_vault.crust.config” file.
You can use the screen utility to avoid maintaining a window constantly opened for each vault. You can also use the tee command to display output to the screen and simultaneously store it in a log file. For example, to launch the first vault the commands could be:
screen -S SV
RUST_LOG=info ./safe_vault -f | tee vault.log
Ctrl-A + Ctrl-D
screen -r SV each time you want to recall the screen.
For subsequent vaults (on other droplets), do the same except that you must omit the -f argument.
Note: I did that a long time ago for some tests, so I may have forgotten some elements.
Client side, an empty string must be entered instead of an invitation token. This is OK for a private network you control. But if your network is public, things are more complex because to avoid spams you must manage invitations. Source of gen_invites program is available, but I don’t know how it works.
If you only need a network for some internal tests, the simplest way is to keep your “SAFE Browser.crust.config” file secret, so that nobody outside your company can connect to your network.