Agora Bridge is the write-side component of the Agora stack. WhileDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/flancian/garden/llms.txt
Use this file to discover all available pages before exploring further.
agora-server handles reading and rendering content, the bridge is responsible for pulling content in from external sources, running bots, and managing integrations with social platforms. Every garden that appears in your Agora gets there because the bridge fetched it.
How the bridge works
The bridge runs as a persistent service that reads a central configuration file (bridges.yaml) and executes fetch or sync tasks in a loop. Each task is called a bridge and has a direction:
| Type | Direction | Description |
|---|---|---|
input | Read into the Agora | Pulls content from an external source |
output | Write out of the Agora | Pushes content to a target (e.g. filesystem) |
bidirectional | Both | Reads and writes (e.g. a two-way sync) |
agora-server reads it.
Supported sources
As of 2022, the bridge supports ingesting content from:Git
The primary source type. Clones or pulls any public git repository containing markdown or other supported garden formats.
Fedwiki
Pulls content from Federated Wiki instances into the Agora node graph.
Mastodon
Ingests toots and interactions from Mastodon accounts or feeds.
Pulls tweets containing wikilinks and stores references to them in the Agora.
bridges.yaml
bridges.yaml is the main configuration file for the bridge service. You can pass it to the service as a command-line parameter. It defines all active bridges — which sources to pull from and what to do with the content.
The bridge reads
agora/gardens.yaml (your Agora’s source list) and bridges.yaml together. gardens.yaml declares what sources exist; bridges.yaml configures how the bridge interacts with them.Per-user agora.yaml
Each user who participates in an Agora community can publish anagora.yaml file inside their digital garden. This file configures the Agora’s behaviour for that user — which actions to take, which outputs to enable, and how their content should be treated.
Signing up users to your Agora
When someone wants to join your Agora, the process is:User publishes agora.yaml
The user adds an
agora.yaml to their garden repository (or any publicly accessible URL) with their source information and any Agora action preferences.Add their garden to gardens.yaml
Add the user’s repository URL to your Agora root’s
gardens.yaml (or sources.yaml). This is the authoritative list of gardens your Agora includes.Running the bridge
After setup (see Self-hosting guide), start the bridge with:Community and contributions
Join the community chat
Join the community chat
If you have questions about configuring the bridge, join the Agora Matrix room.
Add your garden via pull request
Add your garden via pull request
Developers can send a pull request to the reference Agora repository to add their garden directly. For the development discussion room, see the Agora development room.