docs: Add production deployment guide with step-by-step instructions

[YaronZaki]

Problem Statement

No production deployment documentation exists. The CD pipeline (.github/workflows/cd.yml) has inline comments but no standalone deployment guide. docs/contract_deploy.md is minimal. New DevOps team members cannot deploy without tribal knowledge.

Evidence

# .github/workflows/cd.yml has deployment steps but no external documentation
# docs/contract_deploy.md is minimal (<50 lines)
# No docs/deployment.md or equivalent

Impact

Medium — operational risk. Incident recovery procedures are undocumented. New DevOps members cannot deploy without hand-holding. Production environment setup steps are not codified.

Proposed Solution

Create docs/deployment.md covering: environment setup (server specs, domain, SSL), Docker image build, database migration, contract deployment, health check verification, rollback procedure, common troubleshooting.

Acceptance Criteria

• docs/deployment.md created with step-by-step deployment instructions
• Covers: prerequisites, env vars checklist, docker compose up, migration, health check, rollback
• Links to docs/environment_variables.md for configuration reference
• README.md links to deployment guide

File Map

• docs/deployment.md — New: production deployment guide
• README.md — add link to deployment guide

Testing Strategy

• Manual: Follow the deployment guide steps to verify they work on a fresh environment.

Security Considerations

Ensure deployment guide doesn't expose sensitive infrastructure details (IPs, usernames). Use placeholders.

Definition of Done

• Document created and committed
• Guide verified by a team member
• PR linked and merged

---

Labels: documentation
Priority: Medium
Difficulty: Intermediate
Estimated Effort: 2h

[wolfyres]

Hi team,

​I’d like to claim this issue to eliminate the "tribal knowledge" barrier and establish a bulletproof, production-grade deployment guide. Extracting the deployment logic from CD workflow comments into structured, accessible documentation is critical for onboarding and incident recovery.

With a strong background in software infrastructure and Web3 systems, I understand how crucial readable DevOps documentation is for high-stakes production environments. I know exactly how to translate raw YAML workflows and minimal contract deployment steps into clear, actionable, technical runbooks that anyone on the team can execute during an incident.

​⏱️ Timeline
​I can deliver a comprehensive markdown draft for your review within 48 hours of assignment.

​Let me know if I can get started on this!

[grantfox-oss]

🦊 GrantFox — @wolfyres has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #70)
2. Your PR will be reviewed by the Quantarq maintainers

Good luck! Track your progress on GrantFox.