Understanding Nextcloud HaRP: The Future of External App Integration Nextcloud HaRP (Nextcloud AppAPI HaProxy Reverse Proxy) is a reverse proxy system designed to simplify and optimize the deployment of external apps ( ExApps ) within the Nextcloud ecosystem . Introduced as the recommended solution for Nextcloud 32+ , HaRP serves as a modern successor to the older Docker Socket Proxy (DSP) method, offering improved performance, better security, and support for real-time protocols like WebSockets. Core Functions and Architecture HaRP sits behind your main reverse proxy and acts as a dedicated bridge for communication between the Nextcloud server, the client UI, and ExApps. Bypassing the PHP Stack: Traditionally, requests to external apps had to pass through the Nextcloud PHP stack. HaRP allows the web UI to communicate directly with ExApps, significantly reducing resource consumption and improving responsiveness. FRP-Based Tunneling: HaRP utilizes Fast Reverse Proxy ( FRP ) to create secure outbound tunnels from ExApps to the HaRP container. This means ExApps do not need to expose any ports to the host or be directly reachable by the Nextcloud server, which is ideal for restrictive firewall environments. WebSocket Support: One of the most significant upgrades in HaRP is its native support for WebSockets . This enables ExApps to provide real-time features that were previously difficult or impossible to implement under the old proxy system. Key Benefits over Docker Socket Proxy (DSP) While DSP is still supported for the time being, it is slated for deprecation in Nextcloud 35. HaRP offers several advantages that make it the superior choice for modern deployments: Docker Socket Proxy (DSP) Nextcloud HaRP Performance High overhead (PHP proxied) Low overhead (Direct proxying) Connectivity Requires port exposure No ports need exposure (FRP Tunnel) Protocols Limited HTTP support Full HTTP/HTTPS & WebSockets Security Shared Docker socket risks Isolated FRP-based transport Deployment Local host only Local or Remote host support Deployment and Configuration Deploying HaRP involves setting up a dedicated container and then registering it within the Nextcloud administrative interface. docs.nextcloud.comhttps://docs.nextcloud.com Adapting ExApps to HaRP - Nextcloud Documentation
The query " harp nextcloud " refers to HaRP (Nextcloud AppAPI HaProxy Reverse Proxy), a critical system designed for Nextcloud developers and self-hosters to handle External Apps (ExApps) more efficiently . What is HaRP? HaRP is a high-performance reverse proxy that simplifies how Nextcloud communicates with apps running outside the main server (ExApps). It was introduced primarily to: Enable WebSockets: Before HaRP, ExApps struggled with real-time features. HaRP allows end-to-end WebSocket connections for live chats, collaborative editing, and dashboards. Improve Performance: It bypasses the traditional, slower PHP stack for specific app traffic, routing requests directly from the client to the ExApp. Simplify Deployment: It replaces older, more complex setups (like DockerSocketProxy) and uses FRP-based transport to allow ExApps to connect even without exposing ports to the host. Integrating HaRP into Your Stack If you are managing a Nextcloud instance and want to "make" this piece work, here are the core integration points: Deployment Type Key Integration Step All-In-One (AIO) Requires setting a shared key ( HP_SHARED_KEY ) and optionally extending the Apache vhost template to route /exapps/ to the HaRP container. Docker Compose Add the nextcloud-appapi-harp image to your compose file. It typically listens on port 8780 for proxying. Kubernetes (Helm) Use a custom Nginx server block to route /exapps/ traffic directly to the internal nextcloud-harp service. Why it Matters Now Starting with Nextcloud 32 , HaRP is the recommended way to handle external applications. The older systems are being deprecated and are scheduled for removal in Nextcloud 35 . If you are developing an app, you can follow the official Nextcloud ExApp HaRP Integration guide to ensure your app remains compatible with future versions. Adapting ExApps to HaRP - Nextcloud Documentation
In the evolving landscape of self-hosted microservices, HaRP (High-performance AppAPI Reverse Proxy) represents a fundamental shift in how Nextcloud interacts with external applications. Introduced for Nextcloud 32+ , HaRP replaces the legacy Docker Socket Proxy (DSP) system, offering a more robust, scalable way to integrate specialized tools—like AI assistants or real-time collaboration editors—directly into your Hub . The Core Philosophy of HaRP At its heart, HaRP acts as a dedicated traffic controller for the Nextcloud AppAPI . Unlike the old method that forced all traffic through the heavy Nextcloud PHP process, HaRP creates a direct bypass . Bypassing the Bottleneck: It routes client requests directly to External Apps (ExApps) , drastically reducing latency and freeing up server resources. Protocol Freedom: By moving away from purely PHP-based routing, HaRP finally enables full WebSocket support for ExApps. This means real-time features like instant chat updates and collaborative whiteboarding no longer rely on inefficient "polling". Zero-Config Tunneling: Using the FRP (Fast Reverse Proxy) protocol, HaRP allows ExApps to initiate outgoing connections. This eliminates the need to open risky firewall ports or manage complex NAT rules. Architectural Impact HaRP is designed for distributed power . It allows you to run resource-heavy applications—such as AI models requiring high-end GPUs—on separate physical hardware while maintaining a seamless user experience within the main Nextcloud interface. A single HaRP instance can even manage up to 99 different Docker Engines across your network. Why You Should Care If you are a maintainer or power user, the message from the Nextcloud Developer Manual is clear: DSP is legacy . It is scheduled for removal in Nextcloud 35. Switching to HaRP now ensures your ecosystem is future-proof, more secure with its built-in brute-force protection, and significantly faster. Are you planning a migration from DSP or starting a fresh Nextcloud 32 install? I can help you with: The docker-compose configuration for a HaRP setup. Integrating ExApps on a remote GPU server. Configuring NGINX or Caddy to sit in front of HaRP. AIO and HARP for ExApp running remotely - ℹ️ Support
HaRP (High-performance AppAPI Reverse Proxy) is a specialized reverse proxy system introduced to streamline the deployment and performance of External Apps (ExApps) within the Nextcloud ecosystem. Recommended for Nextcloud 32+ deployments, it acts as a modern replacement for the older Docker Socket Proxy (DSP) workflow. Core Functions & Architecture Direct Communication: HaRP allows clients and the Web UI to communicate directly with ExApps, bypassing the Nextcloud PHP stack. This significantly reduces server load and improves response times. WebSocket Support: Unlike previous integration methods, HaRP enables end-to-end WebSockets , which are essential for real-time features like collaborative editing and instant chat. FRP Tunneling: It utilizes Fast Reverse Proxy (FRP) to create secure tunnels between the HaRP container and ExApps. This means ExApp containers don't need to expose ports to the host, simplifying networking and providing NAT traversal. Flexible Deployment: HaRP supports local setups or remote deployments, allowing users to offload heavy workloads (like AI processing on GPUs) to separate machines. Key Benefits Simplified Workflow: Replaces complex DockerSocketProxy setups with a single, easier-to-manage container. Enhanced Security: Includes built-in brute-force protection and dynamic routing to secure exposed interfaces. Future-Proofing: Nextcloud has marked the older DSP method for removal by Nextcloud 35, making HaRP the definitive path for future app development. How to Use HaRP Installation: Launch the HaRP container alongside your Nextcloud instance. Registration: In the Nextcloud Admin Documentation , navigate to AppAPI settings and register a "HaRP Proxy" daemon using your shared secret key. Proxy Configuration: Update your main reverse proxy (e.g., Nginx, Apache) to redirect specific app requests to the HaRP container. App Adaptation: Developers must include a start.sh script in their ExApp Docker images to initialize the FRP client and connect to the proxy. WebSockets in Nextcloud: creating real‑time apps via AppAPI harp nextcloud
HaRP (High-performance AppAPI Reverse Proxy) is the modern networking backbone for Nextcloud’s External Apps (ExApps) ecosystem . Introduced as the recommended deployment daemon starting with Nextcloud Hub 32 , HaRP replaces the older Docker Socket Proxy (DSP) to provide better performance, easier remote deployments, and native support for real-time protocols like WebSockets. What is Nextcloud HaRP? HaRP is a specialized reverse proxy system designed to sit between your main web server (like Nginx or Apache) and individual External Apps. While traditional Nextcloud apps are written in PHP and run within the core server process, ExApps are standalone microservices—often written in Python, Rust, or Go—that run in their own Docker containers. HaRP serves two primary functions: Deployment Management: It communicates with the Docker Engine to create, start, and stop ExApp containers. Traffic Routing: It routes client requests directly to these containers, bypassing the Nextcloud PHP stack entirely for improved efficiency. Key Benefits of HaRP over Docker Socket Proxy (DSP) WebSocket Support: Unlike the legacy proxy, HaRP enables full end-to-end WebSocket communication, allowing ExApps to feature real-time collaborative editing and live dashboards. NAT Traversal with FRP: HaRP uses Fast Reverse Proxy (FRP) tunnels. This means ExApp containers do not need to expose any ports to the host or even be directly reachable by the Nextcloud server. Simplified Remote Deployment: HaRP makes it significantly easier to run ExApps on a different physical server than the main Nextcloud instance. Improved Security: By using a shared key and dedicated certificates, HaRP provides a more robust security model for managing external microservices. How to Install and Configure HaRP For most users, especially those using Nextcloud All-in-One (AIO), HaRP is being integrated as the default option. WebSockets in Nextcloud: creating real‑time apps via AppAPI
Harp + Nextcloud — Brief Write-up Summary Harp is a static site server and build tool that compiles HTML templates, Markdown, and assets into a static site. Nextcloud is a self-hosted file sync and collaboration platform. Integrating Harp with Nextcloud is useful when you want to host or serve a static site from Nextcloud storage (for previews, sharing, or simple hosting behind a Nextcloud-enabled webserver), or use Nextcloud as a source for site content/assets while building with Harp. Use cases
Store Harp project files in Nextcloud to sync across devices and collaborators. Build static sites locally with Harp while source files live in a Nextcloud-synced folder. Serve built Harp output via a webroot that Nextcloud’s webserver (Apache/Nginx with PHP) can expose. Use Nextcloud as a simple remote backup and versioned storage for Harp projects. Understanding Nextcloud HaRP: The Future of External App
Typical workflows
Local development with Nextcloud sync:
Place your Harp project inside a Nextcloud-synced folder on your machine. Run harp server locally to preview; edits sync to Nextcloud automatically. Bypassing the PHP Stack: Traditionally, requests to external
Build then deploy to Nextcloud webroot:
Run harp compile <project> <output_dir> . Copy the compiled output into Nextcloud’s external web-accessible directory (e.g., a subfolder served by your webserver or Nextcloud’s "Public" folder if configured).