Skip to content

rfc: Forge-Central Deployment Strategy - #22

Merged
bajtos merged 5 commits into
mainfrom
forge-central-deployment-strategy
Aug 17, 2026
Merged

rfc: Forge-Central Deployment Strategy#22
bajtos merged 5 commits into
mainfrom
forge-central-deployment-strategy

Conversation

@bajtos

@bajtos bajtos commented Aug 13, 2026

Copy link
Copy Markdown
Member

馃摉 Preview

Summary

Forge consists of two independent sets of services: Forge-Central contains centrally managed set of services operated by the FilOne team, FilOne Appliance contains the software stack powering regional nodes.

This pull request proposes deployment strategy for the Central stack. It's a complement for rfc#19, which describes the deployment strategy for FilOne Appliance.

Proofs of Concept

Signed-off-by: Miroslav Bajto拧 <oss@bajtos.net>
Copilot AI lite review requested due to automatic review settings August 13, 2026 16:51

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a new RFC describing the proposed deployment and operations strategy for the Forge-Central (centrally managed) service stack, complementing RFC #19 which covers the FilOne Appliance (regional nodes).

Changes:

  • Documents requirements/constraints and non-requirements for Forge-Central deployments.
  • Proposes an AWS/ECS Fargate + RDS/OpenBao/Terraform-based architecture and Terraform workspace/module layout.
  • Describes secret/key provisioning via a Go Lambda and outlines a GitHub Actions-driven continuous delivery/promotion flow, with alternatives considered.

馃挕 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread rfcs/2026-08-forge-central-deployment-strategy.md Outdated
Comment thread rfcs/2026-08-forge-central-deployment-strategy.md Outdated
Comment thread rfcs/2026-08-forge-central-deployment-strategy.md Outdated
Comment thread rfcs/2026-08-forge-central-deployment-strategy.md Outdated
Comment thread rfcs/2026-08-forge-central-deployment-strategy.md Outdated
Comment thread rfcs/2026-08-forge-central-deployment-strategy.md Outdated
Comment thread rfcs/2026-08-forge-central-deployment-strategy.md Outdated
Comment thread rfcs/2026-08-forge-central-deployment-strategy.md Outdated
Comment thread rfcs/2026-08-forge-central-deployment-strategy.md Outdated
bajtos and others added 2 commits August 13, 2026 18:57
Signed-off-by: Miroslav Bajto拧 <oss@bajtos.net>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Comment thread rfcs/2026-08-forge-central-deployment-strategy.md Outdated
Co-authored-by: Miroslav Bajto拧 <oss@bajtos.net>

@hannahhoward hannahhoward left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love it when I can just LGTM a PR. Unless you feel strongly I'd file Palumi under "yea that might be nice but we should stick to what's known".

Signed-off-by: Miroslav Bajto拧 <oss@bajtos.net>
@bajtos
bajtos merged commit aec5db5 into main Aug 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants