Conversation
|
Failed with this bug on Linux only. |
|
Ubuntu 20.04.2 unzip not found |
BitcoinOG
left a comment
There was a problem hiding this comment.
Just ran this. Weirdly I don't get the unzip not found error today, just the shell exiting when I choose testnet:
~$ export BRANCH=feat/interactive-setup
~$ sh -c "$(curl -sfL https://raw.githubusercontent.com/opendexnetwork/opendex-docker/feat/interactive-setup/opendex.sh)"
Installing opendex-launcher v1.0.0-rc.5 ...
https://github.com/opendexnetwork/opendex-launcher/releases/download/v1.0.0-rc.5/opendex-launcher-linux-amd64.zip
1) Testnet
2) Mainnet
Please choose the network: 1
~$
Fixed by using |
You could run Probably related to this issue: opendexnetwork/opendex-launcher#3 |
|
Ran this on testnet, basic setup is working 🎉 |
|
Noticed these smaller issues:
|
BitcoinOG
left a comment
There was a problem hiding this comment.
Exits here...
Syncing light clients:
┌─────────┬───────────────────────────────────────────────────┐
│ SERVICE │ STATUS │
├─────────┼───────────────────────────────────────────────────┤
│ lndbtc │ Syncing 100.00% (1940583/1940583) │
├─────────┼───────────────────────────────────────────────────┤
│ lndltc │ Syncing 100.00% (1843256/1843256) │
└─────────┴───────────────────────────────────────────────────┘
Do you want to create a new opendexd environment or restore an existing one?
1) Create New
2) Restore Existing
Please choose: 1
ERROR: type not a pointer: string
~/.opendex-docker
|
Same when re-entering env, all I did was pressing |
BitcoinOG
left a comment
There was a problem hiding this comment.
One small bug to fix: enter the OpenDEX console instead of throwing the Create New / Restore Existing selection again, when this is fixed we can merge:
~/.opendex-docker$ sh -c "$(curl -sfL https://raw.githubusercontent.com/opendexnetwork/opendex-docker/feat/interactive-setup/opendex.sh)"
Installing opendex-launcher v1.0.0-rc.5 ...
https://github.com/opendexnetwork/opendex-launcher/releases/download/v1.0.0-rc.5/opendex-launcher-linux-amd64.zip
1) Testnet
2) Mainnet
Please choose the network: 1
🚀 Launching testnet environment
🌍 Checking for updates ...
🏃 Warming up ...
Syncing light clients:
┌─────────┬───────────────────────────────────────────────────┐
│ SERVICE │ STATUS │
├─────────┼───────────────────────────────────────────────────┤
│ lndbtc │ Syncing 100.00% (1964007/1964007) │
├─────────┼───────────────────────────────────────────────────┤
│ lndltc │ Syncing 100.00% (1845256/1845256) │
└─────────┴───────────────────────────────────────────────────┘
🕹️ Loading OpenDEX console ...
Do you want to create a new opendexd environment or restore an existing one?
1) Create New
2) Restore Existing
Please choose: 1
You are creating an opendex node key and underlying wallets. All will be secured by a single password provided below.
Enter a password:
Re-enter password:
----------------------BEGIN OpenDEX SEED---------------------
1. abandon 2. trick 3. palm 4. spot
5. hover 6. fringe 7. you 8. upgrade
9. rice 10. early 11. lock 12. cup
13. lemon 14. man 15. chunk 16. staff
17. clump 18. try 19. frog 20. mind
21. garment 22. fork 23. venture 24. silver
-----------------------END OpenDEX SEED----------------------
Please write down your 24 word mnemonic. It will allow you to recover your OpenDEX node key and on-chain funds for the initialized wallets listed above should you forget your password or lose your device. Off-chain funds in channels can NOT be recovered with it and must be backed up and recovered separately. Keep it somewhere safe, it is your ONLY backup in case of data loss.
The following wallets were initialized: BTC, LTC, ETH
Do you want to create a new opendexd environment or restore an existing one?
1) Create New
2) Restore Existing
|
Other than that, when I exited and entered the env again, the OpenDEX console loaded, |
1. Why is this pull request needed and what does it do?
This PR brings old xud-docker CLI interactive setup flow back.
Network selection
Update checking
Syncing indicator
Wallet setup question
Auto-unlock question
Backup setup question
The most familiar console
2. Which issues (if any) are related?
Close #7.
3. Which documentation changes (if any) need to be made?
https://opendex.network/docs/swap-providers#lets-roll
4. Does this introduce a backward incompatible change or deprecation?
It may affects the old non-interactive setup flow.
5. How to test?
Todos
statuscommand missingInteractive update checking