update deployment guide for bitcoin payments
This commit is contained in:
@@ -2,8 +2,7 @@
|
|||||||
|
|
||||||
## 1. Requirements
|
## 1. Requirements
|
||||||
|
|
||||||
- Ubuntu 22.04+ (or similar Linux)
|
- Ubuntu 22.04+ or similar Linux with Docker Engine and the Compose plugin — follow [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository). Tested and recommended on Ubuntu 22.04 LTS.
|
||||||
- Docker Engine and Compose plugin — follow [Install Docker Engine on Ubuntu](https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository)
|
|
||||||
- A domain name pointing at your server (A record for clearnet HTTPS)
|
- A domain name pointing at your server (A record for clearnet HTTPS)
|
||||||
|
|
||||||
## 2. Server setup
|
## 2. Server setup
|
||||||
@@ -49,6 +48,7 @@ Edit `.env.prod`. Mandatory configuration:
|
|||||||
| `SHOP_FIAT_CURRENCY` | `USD`, `EUR`, `GBP`, `CAD`, `AUD`, or `CHF` |
|
| `SHOP_FIAT_CURRENCY` | `USD`, `EUR`, `GBP`, `CAD`, `AUD`, or `CHF` |
|
||||||
| `SIGNED_COOKIE_JWT_SECRET` | strong random secret |
|
| `SIGNED_COOKIE_JWT_SECRET` | strong random secret |
|
||||||
| `BASE64_ENCRYPTION_KEY` | generate with `openssl rand -base64 32` |
|
| `BASE64_ENCRYPTION_KEY` | generate with `openssl rand -base64 32` |
|
||||||
|
| `PAYMENT_METHODS_ENABLED` | e.g. `xmr,btc` |
|
||||||
| `MONERO_NETWORK` | `mainnet` |
|
| `MONERO_NETWORK` | `mainnet` |
|
||||||
| `MONERO_DAEMON_ADDRESS` | mainnet node `host:port` |
|
| `MONERO_DAEMON_ADDRESS` | mainnet node `host:port` |
|
||||||
| `MONERO_WALLET_RPC_USERNAME` | strong random username |
|
| `MONERO_WALLET_RPC_USERNAME` | strong random username |
|
||||||
@@ -61,11 +61,9 @@ Edit `.env.prod`. Mandatory configuration:
|
|||||||
| `VITE_API_BASE_URL` | `/api` |
|
| `VITE_API_BASE_URL` | `/api` |
|
||||||
| `VITE_SHOP_FIAT_CURRENCY` | same as `SHOP_FIAT_CURRENCY` |
|
| `VITE_SHOP_FIAT_CURRENCY` | same as `SHOP_FIAT_CURRENCY` |
|
||||||
|
|
||||||
Optional — adjust Monero payment confirmation rules:
|
Optional — adjust per-method payment confirmation rules (`MONERO_CONFIRMATION_TIERS`, `BITCOIN_CONFIRMATION_TIERS`). Each is a JSON array with the same shape. For each order, the shop uses `minConfirmations` from the first tier where the order total (in `SHOP_FIAT_CURRENCY`) is `<= upToTotalFiat`. The last tier is a catch-all and must omit `upToTotalFiat`. At most one tier may use `minConfirmations: 0` (accept unconfirmed / mempool); that tier cannot be the catch-all.
|
||||||
|
|
||||||
**`MONERO_CONFIRMATION_TIERS`** — JSON array. For each order, the shop uses `minConfirmations` from the first tier where the order total (in `SHOP_FIAT_CURRENCY`) is `<= upToTotalFiat`. The last tier is a catch-all and must omit `upToTotalFiat`. At most one tier may use `minConfirmations: 0` (accept on mempool); that tier cannot be the catch-all.
|
Monero example (default in `.env.example`):
|
||||||
|
|
||||||
Example (default in `.env.example`):
|
|
||||||
|
|
||||||
```json
|
```json
|
||||||
[
|
[
|
||||||
|
|||||||
Reference in New Issue
Block a user