Nextcloud is only as reliable as its underlying storage. Traditional Network Attached Storage (NAS) can become a bottleneck. The HARP framework favors distributed object storage systems like Ceph, MinIO, or AWS S3. Object storage allows concurrent read/write operations across millions of files without file-locking lag. 4. Performance Optimization
| Feature | HaRP | DockerSocketProxy | |---------|------|--------------------| | | 32+ | Any | | WebSocket Support | Yes (full) | No | | Latency | Lower (bypasses Nextcloud) | Higher (routes through Nextcloud) | | Deployment Complexity | Moderate (one container + reverse proxy config) | Higher (multiple moving parts) | | Remote ExApp Support | Yes (with manual install) | Limited | | Future Support | Recommended path forward | Deprecated | harp nextcloud
The flow is relatively straightforward: a user initiates a request to an ExApp from the Nextcloud web interface. That request hits your main reverse proxy (NGINX, Caddy, Apache, etc.), which forwards it to HaRP. HaRP, in turn, validates the user’s session with Nextcloud to ensure the request is legitimate. Once validated, the request is routed directly to the ExApp container’s network endpoint. For WebSocket traffic, HaRP maintains a persistent connection between the client and the ExApp, allowing for low‑latency, bi‑directional communication. Nextcloud is only as reliable as its underlying storage
The to your primary Nextcloud environment. That request hits your main reverse proxy (NGINX,
Introduced as the standard architecture for modern deployments, . By integrating Fast Reverse Proxy (FRP) tunneling and an enterprise-grade HAProxy base, it natively addresses these limitations. Core Technical Architecture of HaRP
The routes its docker socket across the secure FRP tunnel.