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

# Router testing notes

We're using this space to collect feedback on how we can improve with running the provider on router hardware.

Below is a table of router and device models, architecture, and notes when running. Please add notes and links to gists/repos of any relevant scaffolding to set up the provider in the section below. Over time we will fold these into [the provider docs](https://docs.ur.io/provider).

## Provider binary

Download the `urnetwork-provider-XXX.tar.gz` from [releases](https://github.com/urnetwork/build/releases) to get binaries for many architectures:

```
linux/
    386
    amd64
    arm
    arm64
    mips
    mips64
windows/
    amd64
    arm64
darwin/
    amd64
    arm64
```

Or use the community docker image:

```
docker pull bringyour/community-provider:latest
docker run -ti bringyour/community-provider:latest --help
```

## Notes

Please submit PRs to edit this.

| Model        | Architecture | Notes                                                                                                         |
| ------------ | ------------ | ------------------------------------------------------------------------------------------------------------- |
| Raspberry Pi | arm64        | Setting up the provider to run with systemctl works well. It also works to run the provider inside of docker. |


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.ur.io/router/testing-notes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.