WebSockets in Nextcloud: creating real‑time apps via AppAPI
fn append_metadata(prev_hash: &[u8; 32], meta: &Metadata) -> [u8; 32] let mut hasher = Sha3_256::new(); hasher.update(meta.serialize()); hasher.update(prev_hash); hasher.finalize().into()
The appapi in Nextcloud is configured to use HaRP as its proxy for managing ExApps . harp nextcloud
While traditional setups often rely on the main web server (like Apache or Nginx) to handle all traffic, HaRP introduces a dedicated, lightweight, and high-performance layer designed to handle the unique communication needs of containerized extensions. It is crucial for AppAPI-based deployments, particularly when managing multi-Docker environments and handling real-time data. Key Features and Benefits of HaRP
Some users have reported that after rebooting the host server, HaRP can no longer communicate with the Docker daemon until the container is manually restarted. The workaround is to add --restart unless-stopped to your docker run command (as shown in the installation examples) or to use Docker Compose with a restart: unless-stopped policy. Key Features and Benefits of HaRP Some users
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
By bypassing the heavy PHP stack and routing traffic directly from the client to the ExApp, HaRP significantly reduces response times. Security & Simplified Networking: Traditional Network Attached Storage (NAS) can become a
. The old DSP method is slated for deprecation and removal by Nextcloud 35 Persistence:
Think of HaRP as a high-performance bridge that efficiently routes requests between users, your Nextcloud server, and the external apps that extend its functionality.
The official GitHub repository describes HaRP as a tool that “enables direct communication between clients and ExApps, bypassing the Nextcloud instance to improve performance and reduce the complexity traditionally associated with DockerSocketProxy setups”. In practice, this means that when someone uses an external app – whether it’s a live transcription tool, a chat interface, or a collaborative whiteboard – their traffic no longer has to travel through Nextcloud’s main application layer before reaching the microservice that actually powers the feature.
The combination of HARPs and Nextcloud can enable a range of exciting use cases: