Following this tutorial:
You should run at least
min_section_size
instances of the vault binary before trying to connect any clients
Then in your browser directory, where the executable resides, replace peruse.crust.config
with the contents of safe_vault.crust.config
that you created to run your local vaults.
Exception for OSX users: Use this example to observe where the crust.config
file should reside.
NOTE: at the time of writing the latest release for download is still named Peruse. Subsequent versions will be named SAFE Browser
, so you’d then be replacing safe-browser.crust.config
, not peruse.curst.config
.
Now execute your browser and it should connect to your local test net.
For those whom are building SAFE Browser yourselves and want to use yarn prod-dev
instead of packaging it:
- Replace the contents of the crust.config file with the contents of the
safe_vault.crust.config
file that you created to run your local vaults. - Run one of these three commands based on your platform
yarn prod-dev
, assuming you’ve alreadyyarn
,yarn rebuild
,yarn build
, see README.
As always, let me know your issues so we can get you sorted.