bitshares / bitshares/bitshares-core
Support running cli_wallet via Docker
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 660
- Avg merge
- 8h 17m
- Merged PRs (30d)
- 26
Description
**User Story**
As a user I'd like that cli_wallet can be used via docker. An example is here: https://github.com/ichuan/bitshares-docker .
As of writing, we can run cli_wallet like this when the docker instance is running
```
docker exec -it [docker_instance_id] /usr/local/bin/cli_wallet [args]
```
**Impacts**
Describe which portion(s) of BitShares Core may be impacted by your request. Please tick at least one box.
- [ ] API (the application programming interface)
- [ ] Build (the build process or something prior to compiled code)
- [ ] CLI (the command line wallet)
- [x] Deployment (the deployment process after building such as Docker, Travis, etc.)
- [ ] DEX (the Decentralized EXchange, market engine, etc.)
- [ ] P2P (the peer-to-peer network for transaction/block propagation)
- [ ] Performance (system or user efficiency, etc.)
- [ ] Protocol (the blockchain logic, consensus, validation, etc.)
- [ ] Security (the security of system or user data, etc.)
- [ ] UX (the User Experience)
- [ ] Other (please add below)
**Additional Context (optional)**
Add any other context about your request here.
## CORE TEAM TASK LIST
- [ ] Evaluate / Prioritize Feature Request
- [ ] Refine User Stories / Requirements
- [ ] Define Test Cases
- [ ] Design / Develop Solution
- [ ] Perform QA/Testing
- [ ] Update Documentation
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the linked bitshares-docker example and the current cli_wallet invocation, including `docker exec -it [docker_instance_id] /usr/local/bin/cli_wallet [args]`. Done should mean cli_wallet can be used through Docker, but the issue does not define the required image, configuration, or test cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, docker
- Domain
- cli, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100