format the README.md
This commit is contained in:
55
README.md
55
README.md
@@ -1,10 +1,3 @@
|
|||||||
Here’s an **extended README.md** that combines your original usage instructions with the **Makefile workflow** for clarity and ease of onboarding:
|
|
||||||
|
|
||||||
***
|
|
||||||
|
|
||||||
## ✅ Extended `README.md`
|
|
||||||
|
|
||||||
````markdown
|
|
||||||
# hdwalletpy – Setup & Usage Guide
|
# hdwalletpy – Setup & Usage Guide
|
||||||
|
|
||||||
This project provides a Python-based HD Wallet tool with optional Docker-based build automation for fast, reproducible environments.
|
This project provides a Python-based HD Wallet tool with optional Docker-based build automation for fast, reproducible environments.
|
||||||
@@ -16,24 +9,27 @@ This project provides a Python-based HD Wallet tool with optional Docker-based b
|
|||||||
### **Option 1: Standard Python Setup (Host Machine)**
|
### **Option 1: Standard Python Setup (Host Machine)**
|
||||||
|
|
||||||
1. Clone the repository:
|
1. Clone the repository:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
git clone https://github.com/<your-username>/hdwalletpy.git
|
git clone https://github.com/<your-username>/hdwalletpy.git
|
||||||
cd hdwalletpy
|
cd hdwalletpy
|
||||||
````
|
```
|
||||||
|
|
||||||
2. Create a virtual environment:
|
2. Create a virtual environment:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
python -m venv .venv
|
python -m venv .venv
|
||||||
source .venv/bin/activate
|
source .venv/bin/activate
|
||||||
```
|
```
|
||||||
|
|
||||||
3. Install dependencies:
|
3. Install dependencies:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
python -m pip install --upgrade pip
|
python -m pip install --upgrade pip
|
||||||
python -m pip install -r requirements.txt
|
python -m pip install -r requirements.txt
|
||||||
```
|
```
|
||||||
|
|
||||||
***
|
---
|
||||||
|
|
||||||
### **Option 2: Fast Setup Using Docker + Makefile**
|
### **Option 2: Fast Setup Using Docker + Makefile**
|
||||||
|
|
||||||
@@ -79,7 +75,7 @@ make clean # Remove host venv and wheelhouse
|
|||||||
make down # Stop/remove container
|
make down # Stop/remove container
|
||||||
```
|
```
|
||||||
|
|
||||||
***
|
---
|
||||||
|
|
||||||
## ✅ Basic Usage
|
## ✅ Basic Usage
|
||||||
|
|
||||||
@@ -110,14 +106,14 @@ python ./src/pyhdwallet.py fetchkey "https://example.com/key.asc" --out mykey.as
|
|||||||
python ./src/pyhdwallet.py test
|
python ./src/pyhdwallet.py test
|
||||||
```
|
```
|
||||||
|
|
||||||
***
|
---
|
||||||
|
|
||||||
## 🔐 Notes on `--file`, AES ZIP, and PGP
|
## 🔐 Notes on `--file`, AES ZIP, and PGP
|
||||||
|
|
||||||
* `--file` writes **only** an AES-encrypted ZIP (no raw `.json`/`.asc` left on disk), using `pyzipper`.
|
- `--file` writes **only** an AES-encrypted ZIP (no raw `.json`/`.asc` left on disk), using `pyzipper`.
|
||||||
* If `--pgp-pubkey-file` is set, the ZIP contains a single ASCII-armored PGP message (`.asc`) created with PGPy-style `PGPMessage.new(...)` then `pubkey.encrypt(...)`.
|
- If `--pgp-pubkey-file` is set, the ZIP contains a single ASCII-armored PGP message (`.asc`) created with PGPy-style `PGPMessage.new(...)` then `pubkey.encrypt(...)`.
|
||||||
|
|
||||||
***
|
---
|
||||||
|
|
||||||
## ⚠️ About `--force`
|
## ⚠️ About `--force`
|
||||||
|
|
||||||
@@ -130,16 +126,16 @@ python ./src/pyhdwallet.py gen > out.txt # likely refused (non-TTY)
|
|||||||
python ./src/pyhdwallet.py gen --force > out.txt # allowed
|
python ./src/pyhdwallet.py gen --force > out.txt # allowed
|
||||||
```
|
```
|
||||||
|
|
||||||
***
|
---
|
||||||
|
|
||||||
## ✅ Why Use Makefile?
|
## ✅ Why Use Makefile?
|
||||||
|
|
||||||
* **Speed:** Avoid repeated `apt-get` installs; wheels cached locally.
|
- **Speed:** Avoid repeated `apt-get` installs; wheels cached locally.
|
||||||
* **Reproducibility:** Same Docker image for builds; no environment drift.
|
- **Reproducibility:** Same Docker image for builds; no environment drift.
|
||||||
* **Convenience:** One-liner tasks (`make wheels`, `make venv-host`, `make shell`).
|
- **Convenience:** One-liner tasks (`make wheels`, `make venv-host`, `make shell`).
|
||||||
* **Separation:** Host venv vs container venv for clean workflows.
|
- **Separation:** Host venv vs container venv for clean workflows.
|
||||||
|
|
||||||
***
|
---
|
||||||
|
|
||||||
## Common Makefile Targets
|
## Common Makefile Targets
|
||||||
|
|
||||||
@@ -153,22 +149,3 @@ make venv-container # Container venv at /opt/venv
|
|||||||
make down # Stop/remove container
|
make down # Stop/remove container
|
||||||
make clean # Remove .venv_host and wheelhouse
|
make clean # Remove .venv_host and wheelhouse
|
||||||
```
|
```
|
||||||
|
|
||||||
***
|
|
||||||
|
|
||||||
## License
|
|
||||||
|
|
||||||
Add your license info here.
|
|
||||||
|
|
||||||
```
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
✅ This README now **integrates your original usage instructions** with the **Makefile workflow**, so new users can choose between a standard Python setup or the optimized Docker-based approach.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
👉 Do you want me to **also include the Makefile and Dockerfile snippets directly in the README** (so users don’t need to open separate files), or keep them as separate files for clarity?
|
|
||||||
Or should I prepare a **GitHub-ready ZIP** with `README.md`, `Makefile`, `Dockerfile`, and `.gitignore` for you?
|
|
||||||
```
|
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user