Files
proxmox/docs/10-best-practices/BEST_PRACTICES_SUMMARY.md
defiQUG fbda1b4beb
Some checks failed
Deploy to Phoenix / deploy (push) Has been cancelled
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

1.6 KiB

Best Practices Summary

Last Updated: 2026-01-31
Document Version: 1.0
Status: Active Documentation


Quick reference of best practices for validated set deployment.

🔒 Security

  • Use encrypted credential storage
  • Restrict file permissions (600 for sensitive files)
  • Use SSH keys, disable passwords
  • Regularly rotate API tokens
  • Implement firewall rules
  • Use unprivileged containers
  • Encrypt validator key backups

🛠️ Operations

  • Test in development first
  • Use version control for configs
  • Document all changes
  • Create snapshots before changes
  • Use consistent naming conventions
  • Implement health checks
  • Monitor logs regularly

📊 Monitoring

  • Enable Besu metrics (port 9545)
  • Centralize logs
  • Set up alerts for critical issues
  • Create dashboards
  • Monitor resource usage
  • Track consensus metrics

💾 Backup

  • Automate backups
  • Encrypt sensitive backups
  • Test restore procedures
  • Store backups off-site
  • Maintain retention policy
  • Document backup procedures

🧪 Testing

  • Test deployment scripts
  • Test rollback procedures
  • Test disaster recovery
  • Validate after changes
  • Use dry-run mode when available

📚 Documentation

  • Keep docs up-to-date
  • Document procedures
  • Create runbooks
  • Maintain troubleshooting guides
  • Version control documentation

Performance

  • Right-size containers
  • Monitor resource usage
  • Optimize JVM settings
  • Use SSD storage
  • Optimize network settings
  • Monitor database growth