This guide may be relevant to all OS but only has specific instructions for: Linux :no_entry:; Mac :white_check_mark:; Windows :no_entry: Summary During testing it may be beneficial to be able to compare the application behaviour accross multiple builds at the same time. This page describes how to do that. Instructions Create a folder where you will keep and run the builds fromFor example, if you want to create this in your home folder $ mkdir ~/status-instances
5/31/2024![](https://i.imgur.com/bqnMloS.png =220x200) Main focus: Wallet functionality end to end. Members: Anthony, Carl (design), Khushboo, Nastya (QA), Sale, Stefan QA notes can be found in QA standups/notes September 12 (Mon) Anthony
3/28/2024Alice -> Bob: Authentication Request Bob -> Felix: Authenication approval alt Authentication rejected Bob -> Alice: Authetnication rejected end Bob -> Alice: Authentication Response Alice -> Felix: User data request Felix -> Alice: User data response
2/6/2024:warning: Currently we have only 5 tester lincenses. Follow these steps to use the available floating licenses : Generate password protected Ed25519 SSH key with at least 100 rounds of key derivationsssh-keygen -o -a 100 -t ed25519 -f ~/.ssh/id_ed25519 -C "joe@example.com" The public key should be in ~/.ssh/id_ed25519.pub. Create PR for the Squish Server Config in order to add your user and SSH key to the bootstrap__active_extra_users list. Request review from @jakubgs. Once Jakub has deployed the changes You will be able to create an SSH tunnel to one of the Squish license server ports(49345) available under squish.infra.status.im and squish-02.infra.status.im:ssh -N -L 49345:localhost:49345 squish.infra.status.im If your local login is different it has to be specified before the hostname separated by @.ssh -N -L 49345:localhost:49345 joe@squish.infra.status.im :information_source: This command blocks and should be left to run while tunnel is used.
9/20/2023or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up