From 75f4c3c522b4c4bd0d5c0f98a570a58a501b59b0 Mon Sep 17 00:00:00 2001 From: lilia Date: Wed, 12 Apr 2017 20:38:49 -0700 Subject: [PATCH] Update CONTRIBUTING.md Add how-to for storageProfile config // FREEBIE --- CONTRIBUTING.md | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f64994672..048e4ec5f 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -68,10 +68,26 @@ mobile, **you must build a mobile client that targets the staging server** You should now be able to use the extension. -## Chrome profiles +## Storage profiles -Don't have any friends to help you test the extension? Make a couple of Chrome -profiles. Each one will need its own Google account and Google Voice number. +To facilitate registration of multiple clients from one machine/user for +development purposes, you can configure multiple storage profiles and switch +between them using the NODE_APP_INSTANCE environment variable. + +``` +// config/local-alice.json +{ + "storageProfile": "aliceProfile" +} + +> NODE_APP_INSTANCE=alice npm start +``` + +This changes the [userData](https://electron.atom.io/docs/all/#appgetpathname) +directory from `%appData%/Signal` to `%appData%/Signal-aliceProfile`. + +Each profile can be independently linked or registered as standalone. +Each one will need its own Google account and Google Voice number. Each one will have to repeat the setup process documented above, including re-accepting the staging server cert under each profile. This is a tedious process, but once you are done you will be able to send messages back and forth