> For the complete documentation index, see [llms.txt](https://docs.meddler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meddler.io/master.md).

# Meddler: Development Guide

## Components

* **Watchdog**
* **Container Orchestrator** (K8S, Nomad, Docker Swarm)
* **Message Queue** (RabbitMQ)
* **Database** (MongoDB , ElasticSearch)
* **Object Store** (MinIO, S3)
* **Dashboard**
* **API Gateway**
* **Logging Pipeline** (Fluentd)
* **Pikachew** (Log Streamer)
* **Plugins** (Docker Containers)
* **Build Engine** (Watchdog Injector)
* **Registry** (Storage for plugin / docker Images)

## Plugins

A plugin is simply a Docker Image which can be published through:

* Dockerfile
* Package: .tar | .zip: ( Dockerfile must be present in the root directory)
* Git Url ( Dockerfile must be present in the root directory)
  * Public Git Repository
  * Private Git Repository with access token

{% hint style="info" %}
Docker container will by default use read-only file system, and only a handful of directories would be accessible for reading / writing data. Although, it is possible to provision a write-enabled filesystem,  making a read-only compatible plugin is recommended.
{% endhint %}

##  


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.meddler.io/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.