Architecture: Where should Vitto desktop signing secrets be stored?

Documentation for Sessions

🏗️ Architecture: Where should Vitto desktop signing secrets be stored?

Date: 2026-02-25
Time: 15:37:08 UTC
Session: gspace1-141.4
Agent: backend
Confidence: 95%
Status: ✅ Documented

📋 Decision Context

Question:

Where should Vitto desktop signing secrets be stored?

Task: Vitto desktop signing and deployment guide

🎯 Decision Made

Chosen:

GitHub Secrets (repository-level, Actions only). Never Railway env vars, never .env.local.

Options Considered:

GitHub Secrets (Actions CI/CD)
Railway env vars
.env.local
Doppler/HashiCorp Vault

💭 Reasoning

Code signing certs/keys are CI/CD artifacts, not runtime config. Railway env vars are for backend API services at runtime. .env.local is local dev only. GitHub Secrets are encrypted at rest, scoped per-repo, injected only into Actions runs — exactly the right threat model for build-time signing. Mixing signing secrets into runtime environments creates unnecessary attack surface and confusion about what each system owns.

📁 Files Involved

deployment/docs/VITTO-DESKTOP-SIGNING-AND-RELEASE.md
.github/workflows/release-vitto-desktop.yml

🔗 Related

Decision ID: dev_1772033828576_39iw05f
Session: 141
Workspace: gspace1

Auto-generated by MCP Smart Consolidation