Skip to content

Staging deployment + production infra preparation #12

Closed as not planned
Closed as not planned

Description

@alanshaw

This is broader than ms3t — it applies to running the Forge stack as a whole — but ms3t's "stand up a staging deployment" line item is the forcing function that surfaces it.

Why a spike

The decision space is genuinely open: docker-compose (mirrors smelt, fast to ship), Helm (operator-friendly, k8s assumption), Terraform (infra-as-code for cloud), systemd unit files (bare-metal operators). Picking even one right now requires understanding what OSS operators of Forge actually want.

Scope

  • Audit operator personas: who runs Forge, on what substrate?
  • Propose a staging deployment for ms3t-in-sprue + dependencies on a hosted environment we control
  • Propose at least one forward-looking production deploy artifact (helm chart? terraform module? service files?) and justify the choice
  • Initial decision can be docker-based for staging (since smelt already is); the artifact for production is the live question

Acceptance

  • A written proposal as markdown
  • Staging deployment of ms3t exists somewhere reachable
  • Decomposition into follow-up implementation issues
  • OSS operator perspective explicit in the proposal

Activity

  1. changed the title [-]Spike: staging deployment + production infra preparation[/-] [+]Staging deployment + production infra preparation[/+] on Jul 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions