Files

Deploy to Phoenix / deploy (push) Has been cancelled

Details

docs: Ledger Live integration, contract deploy learnings, NEXT_STEPS updates

- ADD_CHAIN138_TO_LEDGER_LIVE: Ledger form done; public code review repo bis-innovations/LedgerLive; init/push commands
- CONTRACT_DEPLOYMENT_RUNBOOK: Chain 138 gas price 1 gwei, 36-addr check, TransactionMirror workaround
- CONTRACT_*: AddressMapper, MirrorManager deployed 2026-02-12; 36-address on-chain check
- NEXT_STEPS_FOR_YOU: Ledger done; steps completable now (no LAN); run-completable-tasks-from-anywhere
- MASTER_INDEX, OPERATOR_OPTIONAL, SMART_CONTRACTS_INVENTORY_SIMPLE: updates
- LEDGER_BLOCKCHAIN_INTEGRATION_COMPLETE: bis-innovations/LedgerLive reference

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-02-12 15:46:57 -08:00

3.3 KiB

Raw Blame History

Proxmox VE Deployment Templates Reference

Last Updated: 2026-02-05
Purpose: List all templates required for Proxmox VE infra deployment and how they are pushed to hosts.

1. LXC OS Templates (per host)

These are downloaded on each Proxmox host via pveam download local <name>. They are not stored in the repo.

Template name	Used by	Notes
`debian-12-standard_12.12-1_amd64.tar.zst`	create-chain138-containers, recreate-ct-2301, config/ip-addresses.conf, create-alltra-nodes	Primary in many scripts
`ubuntu-22.04-standard_22.04-1_amd64.tar.zst`	smom-dbis-138-proxmox (CONTAINER_OS_TEMPLATE), recreate-containers-from-configs, rpc-translator-138	Alternative base
Alpine (e.g. `alpine-3.22-default_*.tar.xz`)	NPMplus container (scripts/npmplus/)	Optional; for NPMplus LXC

Push script: After pushing file templates, run:

bash scripts/push-templates-to-proxmox.sh --download-templates

This runs pveam download local for Debian 12 and Ubuntu 22.04 on each host if not already present.

2. File Templates (pushed to hosts)

Pushed to all three Proxmox hosts (ml110, r630-01, r630-02) under /opt/smom-dbis-138-proxmox/ by:

bash scripts/push-templates-to-proxmox.sh

Besu config templates

Path (on host)	Source
`templates/besu-configs/config-validator.toml`	smom-dbis-138-proxmox/templates/besu-configs/
`templates/besu-configs/config-sentry.toml`
`templates/besu-configs/config-rpc-core.toml`
`templates/besu-configs/config-rpc.toml`
`templates/besu-configs/config-rpc-4.toml`
`templates/docker-compose-besu-temp.yml`	smom-dbis-138-proxmox/templates/

Config files

Path (on host)	Source
`config/proxmox.conf` (if exists) or `config/proxmox.conf.example`	smom-dbis-138-proxmox/config/
`config/genesis.json`
`config/network.conf` / `network.conf.example`

Scripts and lib

scripts/ — full tree (deployment, validation, network, manage, migration, health, upgrade)
lib/ — common.sh, proxmox-api.sh, container-utils.sh, etc.
install/ — besu-validator-install.sh, blockscout-install.sh, firefly-install.sh, etc.

3. Push script usage

Command	Effect
`bash scripts/push-templates-to-proxmox.sh`	Push all file templates and scripts to ml110, r630-01, r630-02
`bash scripts/push-templates-to-proxmox.sh --download-templates`	Same, then run pveam on each host for Debian 12 + Ubuntu 22.04
`bash scripts/push-templates-to-proxmox.sh --dry-run`	Print what would be copied; no SSH/scp

Requirements: SSH access to hosts (from config/ip-addresses.conf: 192.168.11.10, .11, .12). Run from a machine that can reach the Proxmox LAN or has SSH keys configured.

scripts/README.md — Script index
smom-dbis-138-proxmox/README.md — Deployment from that tree
12-quick-reference/QUICK_START_TEMPLATE.md — Using a single template for multiple LXCs
11-references/TEMPLATE_BASE_WORKFLOW.md — Template workflow

3.3 KiB Raw Blame History