For the most recent version and how to install yarn, please refer to yarn documentation and installation guides.
yarn installA config file development.json is required under src/config/.
- To target a locally running node and directory, or fine-tune the config, it's recommended to copy and/or adapt from development.json.sample.
- To target a deployed environment (i.e. DEV, TEST or MVP), it's recommended to copy and/or adapt from development-env.json.sample.
Use below command in order to connect to a locally running infrastructure (see this project:
yarn startIn a testing environment, Alice and Bob are the accounts associated with the legal officers currently powering the Logion wallet. In order to access the legal officer UI, at least one legal officer keypair must be loaded in the Polkadot extension. The first step is to produce the secret seed of one of those accounts. This is achieved with the following command:
subkey inspect SECRET_URI
where SECRET_URI is //Alice for Alice, //Bob for Bob, etc.
This is the list of test accounts' secret seeds:
- Alice:
0xe5be9a5092b81bca64be81d212e7f2f9eba183bb7a90954f7b76361f6edb5c0a - Bob:
0x398f0c28f98885e046333d4a41c19cee4c37368a9832c6502f6cfd182e2aef89 - Charlie:
0xbc1ede780f784bb6991a585e4f6e61522c14e1cae6ad0895fb57b9a205a8f938
In order to register them with the extension:
- Use "Import account from pre-existing seed"
- Encode the secret seed
- Set a password
if you log in with a legal officer address, the logion wallet should show the legal officer interface instead of the regular wallet.
Before releasing a new version of the frontend, the following command should be executed:
yarn pre-release '<p>Some release notes.</p>'This will generate the files required by the new version detection mechanism. The script will automatically create a commit with the changes. The push remains manual. The local copy must be clean before executing the script.