Repository navigation
Confluence tenant for recorded fixtures
LoreMaster edited this page Oct 10, 2026
·
1 revision
The sync is covered end to end by a Go integration test that drives it against a fake
Confluence (an in-process httptest server), so the test suite needs no real tenant and
writes no real pages. See libs/documentation-sync for that test.
A real tenant is still useful for one thing: recording the fixtures (#29 Cloud, #30 Data Center) that let the fake replay real API shapes. That is a maintainer task run locally with credentials in the environment — never from CI, and never against a space you do not own. Nothing here is a secret; the credentials live only in your shell.
- A Confluence Cloud site and a space you own.
- An API token for the account that records: https://id.atlassian.com/manage-profile/security/api-tokens.
- Export for the recorder:
-
CONFLUENCE_BASE_URL— the site's wiki URL, e.g.https://your-site.atlassian.net/wiki. -
CONFLUENCE_EMAIL— the account's email. -
CONFLUENCE_API_TOKEN— the token from step 2.
-
A DC trial, or a local atlassian/confluence Docker image with a trial license, works.
Export CONFLUENCE_DC_BASE_URL and CONFLUENCE_DC_PAT (a personal access token, DC ≥ 7.9).
-
LoreMaster documentation
- A documentation agent that follows the LoreMaster structure
- ADR: One Go engine, thin editor shells
- ADR: Vertical feature slices, in Go and TypeScript
- Choosing what goes where
- Command line
- Confluence editions: the facts the design rests on
- Confluence tenant for recorded fixtures
- Generators: pages written from your project's artifacts
- Getting started: syncing a workspace to Confluence
- GitHub Action: the docs site in one step
- Publishing to a GitHub wiki
- The MCP server
- Two-way sync: pull remote edits back, conflict when both sides change
- Using the MCP server
- Watch mode