Using a separate ssb-server for testing

@RavteCyber

Export environmental variable ssb_appname=ssb-test. That makes ssb-server and ssb-client use ~/.ssb-test instead of ~/.ssb, including automatically making a new secret file in ~/.ssb-test if needed. Then don't follow anyone or use invites from the main network from the test id, or vice versa.
To run it alongside normal ssb, make it use different ports. Put in ~/.ssb-test/config:

{
  "port": 8007,
  "ws": {
    "port": 8988
  }
}

For good measure, set sign and shs caps, as mentioned by @aig in %y00L8pC... and by me in thread %tQakYap..., also referencing @josiah's guide %tWGy2kn.... e.g.:

{
  "port": 8007,
  "ws": {
    "port": 8988
  },
  "caps": {
    "shs": "o9dkRr3BsTYxRJ1dLDXlk0FjPZ0LsP6Tti8PlYUEMU0=",
    "sign": "K84etuJU/BQ5R8eYb0U0I4pUVZfyEcLVlIiKxDg1RAE="
  }
}

@Denis M Goddard yes. If you also set the port config as mentioned, then it can run at the same time as your main instance. If you also set the caps keys as mentioned, it exists in a separate/isolated network. (But note, as @mixmix mentioned in %gOTdlhx..., the sign key should not be changed mid-feed.)

For consistency I would suggest only use ssb_appname=ssb-test for testing/development purposes. Other identities/ssb-servers could use other appnames, e.g. ssb-foo.

There's also ssb-identities for the Node.js stack. That is meant to allow having/using multiple ssb identities in one ssb-server (without needing multiple copies of the database). I don't think I have seen any SSB clients using it though - except Feedless which uses a forked version.