Skip to content

Add Docker Compose Reference Architecture page - #56

Open
fungc-io wants to merge 5 commits into
authgear:mainfrom
fungc-io:compose-reference-architecture
Open

Add Docker Compose Reference Architecture page#56
fungc-io wants to merge 5 commits into
authgear:mainfrom
fungc-io:compose-reference-architecture

Conversation

@fungc-io

@fungc-io fungc-io commented Sep 3, 2026

Copy link
Copy Markdown
Member

Summary

Adds Deployment › Architecture Guides › Docker Compose Reference Architecture, a reference for running Authgear on conventional VMs with Docker Compose or Podman Compose, for deployments where Kubernetes is unavailable or not worth operating.

The page covers:

  • Two datastore options (your own managed datastores, or datastores included on dedicated VMs) across two availability tiers (single instance, high availability), with a VM count table to compare them.
  • An architecture diagram and an inventory of VMs for each of the four resulting setups.
  • Shared requirements: common inventory (domains, certificate, firewall, optional external services), datastore versions, expected capacity, and datastore high availability.
  • Pointers to the firewall, WAF, and backup guidance on the existing On-Premises Reference Architecture page.

Also adds a cross-link from On-Premises Reference Architecture to the new page, and a SUMMARY entry after it.

Diagrams

The diagrams are mermaid architecture-beta blocks. They avoid the align directive (mermaid 11.16+) because the docs site currently ships mermaid 11.14.0, where it produces a syntax error. All four were rendered with mermaid-cli pinned to 11.14.0 to confirm they parse and lay out sensibly.

Files

  • deployment/architecture-guides/docker-compose-reference-architecture.md (new)
  • deployment/architecture-guides/on-premises-reference-architecture.md (cross-link)
  • SUMMARY.md

Adapt the Compose-on-VMs deployment reference into a public architecture
guide alongside the Kubernetes on-premises page. Covers the four setups
(A-D), expected capacity, datastore requirements, and per-setup
inventories. Drop the mermaid align directives, which GitBook's mermaid
11.14.0 rejects, and cross-link from the on-premises page.
Replace the A-D setup matrix with Option 1 (your own datastores) and
Option 2 (included datastores), each with a Non-Production and a
Production setup. Add a Choosing a Setup section with a 2x2 VM-count
table. Diagrams and inventories are unchanged.
Split the setup axes into datastore option and availability tier so
environment names no longer stand in for HA mode. Factor the items
shared by every setup into one Common Inventory table and move shared
requirements after the diagrams. Make headings unique, use one name
per VM role, and drop repeated sentences.
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.

1 participant