asxpio/.env.example
Sergei Poljanski 0fbb6ee809
All checks were successful
Build and Deploy to Production / test (push) Successful in 18s
Build and Deploy to Production / build (push) Successful in 49s
Build and Deploy to Production / deploy (push) Successful in 31s
invoices: multi-crypto payment support
One asset per invoice from a registry (lib/crypto_asset.rb): BTC, LTC,
ETH, XMR, SOL, ALGO, USDT/USDC on ERC-20/TRC-20/BEP-20/Solana/Algorand.
Migration 003 generalizes the ltc_* columns to crypto_* + crypto_coin
(existing LTC invoices backfilled). QR payload adapts per asset: BIP21
amount URIs where supported, bare address for tokens with a network
hint on the PDF. Default addresses come from the CRYPTO_ADDRESSES
secret (JSON code=>address); LTC_ADDRESS still works as legacy.
2026-07-03 02:01:57 +04:00

19 lines
636 B
Bash

RACK_ENV=production
# Generate a fresh value: openssl rand -hex 64
SESSION_SECRET=change-me-to-128-hex-chars
SMTP_ADDR=smtp.fastmail.com
SMTP_PORT=587
SMTP_USER=me@asxp.io
SMTP_PASSWORD=change-me
MAIL_FROM="IE Sergei Poljanski Contact Form <me@asxp.io>"
MAIL_TO=ie@asxp.io
# Optional: default crypto payout addresses prefilled into the new-invoice
# form. JSON object, CryptoAsset code => address (codes in lib/crypto_asset.rb).
# Production sets this from the CRYPTO_ADDRESSES Forgejo secret.
# CRYPTO_ADDRESSES={"BTC":"bc1...","USDT-TRC20":"T..."}
# Legacy: LTC_ADDRESS still fills the LTC default when set.
# LTC_ADDRESS=ltc1...