Mohamed Boudra
c5c2ace698
Documents the daemon-served web UI from #1635: enabling it, reverse proxy, TLS, tunnels, and the auth/exposure model. Adds a community projects page for community-built self-hosting tooling.
22 lines
1.3 KiB
Markdown
22 lines
1.3 KiB
Markdown
---
|
|
title: Community projects
|
|
description: Community-built tools and integrations for Paseo, including self-hosted Docker builds and an alternative relay.
|
|
nav: Community
|
|
order: 7
|
|
category: Getting started
|
|
---
|
|
|
|
# Community projects
|
|
|
|
Projects built by the Paseo community. These **aren't official Paseo projects** and aren't covered by Paseo's support, but they're useful starting points, especially for self-hosting. Review the code before running anything that touches your machine or your agents.
|
|
|
|
## Self-hosting
|
|
|
|
- **[blockfeed/paseo-selfhosted](https://github.com/blockfeed/paseo-selfhosted)**, a Docker build that runs the Paseo web UI connected to a self-hosted local daemon. A good reference if you want a containerized setup. For the built-in way to serve the UI from the daemon, see [Self-hosting the web UI](/docs/web-ui).
|
|
|
|
- **[zenghongtu/paseo-relay](https://github.com/zenghongtu/paseo-relay)**, a lightweight self-hosted relay server for Paseo, written in Go. Run your own relay instead of the hosted one for fully self-hosted remote access. For how the relay fits into Paseo's connection model, see [Security](/docs/security).
|
|
|
|
## Add your project
|
|
|
|
Built something for Paseo, a relay, a deployment recipe, an integration, a client? Open a pull request or an issue on [GitHub](https://github.com/getpaseo/paseo) to get it listed here.
|