Skip to content

fix(DeployConfigurations): remove notice that AIO has a built-in HaRP container as it does not #13948

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
szaimen merged 1 commit into from
Dec 18, 2025
+2 −14
Merged

fix(DeployConfigurations): remove notice that AIO has a built-in HaRP container as it does not #13948

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 2 additions & 14 deletions admin_manual/exapps_management/DeployConfigurations.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,15 +17,15 @@ Orchestrates the deployment of applications as Docker containers.
| The administrator is responsible for the security actions taken to configure the Docker daemon connected to the Nextcloud instance.
| These schemes are only examples of possible configurations.

| For Docker Deploy Daemon (HaRP), `AppAPI HaRP <https://github.com/nextcloud/harp>`_ is required or `AIO HaRP <#nextcloud-in-aio-and-docker-on-the-same-host>`_ for Nextcloud AIO.
| For Docker Deploy Daemon (HaRP), `AppAPI HaRP <https://github.com/nextcloud/harp>`_ is required.
| For Docker Deploy Daemon (Docker Socket Proxy), we recommend that you use the `AppAPI Docker Socket Proxy <https://github.com/nextcloud/docker-socket-proxy>`_ or `AIO Docker Socket Proxy <#nextcloud-in-docker-aio-all-in-one>`_ container for Nextcloud AIO.

There are several Docker Daemon Deploy configurations (example schemes):

* Nextcloud and Docker on the **same host** (via socket, DockerSocketProxy, or HaRP)
* Nextcloud on the host and Docker on a **remote** host (via DockerSocketProxy with HTTPS, or HaRP)
* Nextcloud and **ExApps** in the **same Docker network** (via DockerSocketProxy, or HaRP)
* Nextcloud in AIO Docker and **ExApps** in the **same Docker network** (via AIO DockerSocketProxy or HaRP)
* Nextcloud in AIO Docker and **ExApps** in the **same Docker network** (via AIO DockerSocketProxy)


.. _ai-app_api_ddd-harp:
Expand Down Expand Up @@ -176,18 +176,6 @@ A setup with the HaRP container itself on the remote is not supported.
9. Start the FRP client with the command: ``frpc -c /path/to/frpc.toml``.
10. Finally, test the whole setup with "Test deploy" in the 3-dots menu of the deploy daemon.

Nextcloud in AIO and Docker on the same host
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Nextcloud AIO (All-in-One) comes with a built-in HaRP container that can be used to deploy ExApps on the same host.
Enabling the "HaRP" container should automatically create a Deploy Daemon and configure it to work out-of-the-box.

Just go to AppAPI admin settings and register a ``HaRP All-in-One`` daemon.

.. image:: ./img/harp_aio.png

Finally, test the whole setup with "Test deploy" in the 3-dots menu of the deploy daemon.

.. _ai-app_api_ddd-dsp:

Docker Deploy Daemon (Docker Socket Proxy)
Expand Down