Skip to main content
A source tells MITHUNAI where to read content from. Create it once, then sync it whenever the content changes. For files on your computer, see File uploads.
  1. Open Knowledge and select Connect a knowledge source.
  2. Choose Website, Sitemap, GitHub or File upload, and fill in the fields described below.
  3. Save. The source appears in the list and its first ingestion starts; its status updates as the job runs.
Use Re-sync to ingest changes, and Remove to delete a source.

Sitemap

Reads exactly the URLs listed in a sitemap.xml, without following links. This is the most predictable way to ingest a documentation site: you ingest what you publish, nothing more. Listed URLs must be on the same origin as the sitemap.

Website

Crawls a site from a start URL, following links on the same origin (scheme, host and port). Use it when no sitemap exists. Redirects are not followed, and links to images, media, archives, fonts, stylesheets and scripts are skipped.

GitHub

Reads files from a repository at a branch, tag or commit. By default MITHUNAI skips .git/, node_modules/, vendor/, dist/, build/, target/, .venv/, __pycache__ directories, minified JavaScript and lock files. If you set exclude_paths, include any of those you still want skipped. Repositories are read with the GitHub access your MITHUNAI deployment is configured with. To connect a private repository, ask your MITHUNAI administrator to grant that access. You never paste a token into a source.

Path patterns

In include_paths and exclude_paths: For example, docs/**/*.md,README.md ingests Markdown under docs/ and the root README.

Choose the right source

Security

Source settings are visible to every member of your organisation, so they never hold credentials. Crawls cannot reach private or internal network addresses, and URLs containing a username or password are refused. See Security.
Last modified on September 26, 2026