Skip to content

docs: add self-hosting system configuration page#695

Open
abhijaisrivastava15 wants to merge 5 commits into
devfrom
docs/self-hosting-system
Open

docs: add self-hosting system configuration page#695
abhijaisrivastava15 wants to merge 5 commits into
devfrom
docs/self-hosting-system

Conversation

@abhijaisrivastava15

Copy link
Copy Markdown

What

Adds the System Configuration reference page for self-hosted FutureAGI.

Pages added

  • src/pages/docs/self-hosting/configuration/system.mdx — LLM gateway config.yaml setup (with Steps + Tabs for OpenAI/Bedrock/Vertex), PeerDB replication first-boot fix, Temporal Workers concurrency table

Preview

npm run dev

Then visit: http://localhost:4444/docs/self-hosting/configuration/system

TH-6328

khushalsonawat and others added 3 commits June 26, 2026 13:12
- Lean what/when/architecture overview that routes setup detail to the Configure subfolder
- Keep the architecture diagram and the deployment-options table
- title: sentence case to match sidebar label
- description: remove em-dash, shorten to single purpose line

TH-6329

@khushalsonawat khushalsonawat 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.

Check comments

Comment thread src/pages/docs/self-hosting.mdx Outdated
- **CDC**: PeerDB (continuous Postgres → ClickHouse replication)

**Workflow** — `temporal`
Everything runs on your machines; nothing leaves your network. The full service-by-service breakdown lives in [Configure](/docs/self-hosting/configure)

@khushalsonawat khushalsonawat Jul 2, 2026

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.

Typo, should be /configuration. The Configure card below has it too

Comment thread src/pages/docs/self-hosting.mdx Outdated
<Card title="User Management" icon="user" href="/docs/self-hosting/user-management">
Create accounts via email or Django shell.
<CardGroup cols={3}>
<Card title="Configure" icon="gear" href="/docs/self-hosting/configure">

@khushalsonawat khushalsonawat Jul 2, 2026

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.

Same typo, /configure/configuration

</Card>
<Card title="Troubleshooting" icon="wrench" href="/docs/self-hosting/troubleshooting">
Solutions for every known error.
<Card title="Support" icon="comments" href="/docs/self-hosting/support">

@khushalsonawat khushalsonawat Jul 2, 2026

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.

No coming soon. Implement the new self-hosting sidebar and Support (plus the other missing pages) come with it:

Overview
Requirements
Install
Configuration
  Environment variables
  System configuration
Production
  Checklist
  Security & TLS
  Backups & restore
  Monitoring
  Upgrades & rollback
Troubleshooting & FAQs
Support

description: "Configure the LLM gateway, PeerDB replication, and Temporal workers for your self-hosted instance."
---

## Introduction

@khushalsonawat khushalsonawat Jul 2, 2026

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.

Introduction is a bit bland, rename it. Maybe In this page


## Introduction

A few parts of the stack are configured outside `.env`: the LLM gateway needs a `config.yaml` listing its providers, PeerDB needs its replication mirrors running, and Temporal workers can be tuned for throughput. This page covers all three. Set your secrets and provider keys in [Environment Variables](/docs/self-hosting/configuration/environment) first — the config here references them.

@khushalsonawat khushalsonawat Jul 2, 2026

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.

Drop the em-dash. The env link is right for the new sidebar (env moves under Configuration), just move the page there

<Steps>
<Step title="Copy the Example Config">
```bash
cp futureagi/agentcc-gateway/config.example.yaml \

@khushalsonawat khushalsonawat Jul 2, 2026

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.

Path's off, agentcc-gateway sits at the repo root, not under futureagi/. Same on the mount below. Commands won't run as is


**All-queue (default).** One worker polls every task queue. Controlled by `TEMPORAL_ALL_QUEUES=true` in `.env`. This is the right setup for most self-hosted deployments.

**Per-queue (dev overlay).** Six dedicated workers, one per queue, brought up by the [dev overlay](/docs/self-hosting/install#dev-overlay):

@khushalsonawat khushalsonawat Jul 2, 2026

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.

Install comes with the new sidebar, add it there

## Dive Deeper

<CardGroup cols={2}>
<Card title="Production Checklist" icon="shield" href="/docs/self-hosting/production/checklist">

@khushalsonawat khushalsonawat Jul 2, 2026

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.

Checklist is part of the new Production group, add it with the sidebar

- Fix /configure -> /configuration link typo on the overview (prose + card)
- Rename System configuration opener from Introduction to In this page
- Drop em-dashes across the page (intro + gateway/PeerDB sections)
- Fix gateway config path: agentcc-gateway is at repo root, not under futureagi/
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.

2 participants