Nextcloud Hub 9 Windmill App (Flow)

### 🖼️ Screenshots  <details> <summary>Screenshots</summary> ![image](https://github.com/user-attachments/assets/2ebaa581-0982-41d9-85f3-07e5431ff472) ![image](https://github.com/user-attachments/assets/52ba887c-f85e-4407-af53-92e4124dd7a0) </details>

Shibuya · October 21, 2024, 2:49pm

Ich habe Windmill als externe App installiert, leider stürzt Nextcloud beim Start von Windmill jedes mal ab. Nextcloud ist nach dem Klick auf das Windmill Icon nicht mehr erreichbar. Der Server muss dann neu gestartet werden. Die Protokolle geben leider nach meinem Verständnis nichts her:

Fehlersuche no app in context
OCA\LogReader\Controller\LogController::get uses the @AuthorizedAdminSetting annotation and should use the #[OCP\AppFramework\Http\Attribute\AuthorizedAdminSetting] attribute instead
21.10.2024, 16:45:32
Fehlersuche app_api
Can not find translations for flow ExApp.
21.10.2024, 16:45:23

Ist es noch zu früh oder hat jemand Windmill schon zum Laufen gebracht?

EDIT: I changed the server (2 GB RAM) to one with more RAM (8 GB), now it is working.

q-wertz · October 21, 2024, 3:22pm

Bei uns haben Admin user ein kaputtes Icon in der Appleiste und wenn man darauf klickt lädt die App nicht (man sieht nur den NC Hintergrund).

Nicht sicher ob es richtig installiert wurde aber Schritte die ich so durchgeführt habe:

Docker auf NC Server installiert

sudo apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

Run (according to docker-socket-proxy Readme)

docker run -e NC_HAPROXY_PASSWORD="some_secure_password" \
  -v /var/run/docker.sock:/var/run/docker.sock \
  --name nextcloud-appapi-dsp -h nextcloud-appapi-dsp \
  --restart unless-stopped --privileged -d ghcr.io/nextcloud/nextcloud-appapi-dsp:release

(change some_secure_password)

Add www-data to group docker (didn’t get it working otherwise using the socket)
Reboot your machine

Make sure webhook listeners is enabled

sudo -u www-data ./occ app:enable webhook_listeners

In Administration settings section AppApi create new deploy daemon (I only managed to get other steps working with these settings)

image614×772 52.9 KB

Things that work:

“Check connection” works✅
Test deploy works
Installing external app Flow works

Docker seems to deploy the containers:

root@asdf:/home/user1# docker container ls
CONTAINER ID   IMAGE                                            COMMAND                 CREATED       STATUS                    PORTS     NAMES
946a6c505e24   ghcr.io/cloud-py-api/flow:1.0.1                  "/bin/sh /ex_app_scr…"   2 hours ago   Up 19 minutes                       nc_app_flow
db1bae955880   ghcr.io/nextcloud/nextcloud-appapi-dsp:release   "/bin/bash start.sh"     4 hours ago   Up 19 minutes (healthy)             nextcloud-appapi-dsp

Things that do not work:

Admins see a broken Windmill icon in app list and clicking on it leads to an empty NC window
Normal users do not see the Windmill icon in app list

EDIT:
Entschuldigung für switchen zwischen Englisch und Deutsch

EDIT2:
Mit dem oben habe ich versucht folgende Anleitungen unter einen Hut zu bekommen:

NC Server section “Windmill Workflows”
NC Server section “AppAPI and External Apps”
Docker-socket-proxy Readme

Shibuya · October 23, 2024, 3:04pm

I have now got it to work. Here are some hints, maybe they will help others. I am a beginner, no claim to correctness and completeness.

The Docker Socket Proxy container should be installed during the installation so that ExApps can be installed
Windmill is under external apps in the tools section and is called “Flow”
There should be enough RAM on the server, otherwise Nextcloud will crash
After installing Windmill, switch the workspace to Admin and run the existing flow “Synchronize Hub”.
The Nextcloud data must be entered under Resources, and in particular an app-specific account password must be created.
Windmill lists scripts for Nextcloud actions. Unfortunately, the tinkering starts then.

q-wertz · October 29, 2024, 1:41pm

Sorry I don’t really get what you mean. First three steps are clear to me and but the other two steps I cannot follow:

What do you mean with Admin workspace? As an admin user I have to access the Windmill app? Or do you mean the Windmill settings in the Admin account? Can you access the Windmill app at that point already?

I think in my case something with the NGINX config is wrong or the Docker socket proxy config (which is AFAIK derived from Tecnativas and might require some more configuration that is not described in the Nextcloud manuals).

I opened an issue in the Flow app. But currently do not really have the time to work on debugging it further.

Hints are welcome

Shibuya · October 29, 2024, 4:01pm

Yes, at that point I can access the Windmill app. This step is inside the windmill app at the left bar, where you can chose a windmill workspace.

Did you install the Docker Socket Proxy container in your AIO installation by checking the checkbox?

q-wertz · October 29, 2024, 4:27pm

I don’t have AIO, it’s a “baremetal” manual installation with only Windmill running in the docker

leonis_csem · February 13, 2025, 5:20am

I don’t know if the topic is still active, yet I am also facing trouble with the deployment on a Nextcloud Hub 9 (30.0.5) AIO instance.

AppAPI is configured correctly (coming with Nextcloud AIO by default), dpcker ps -a shows the Docker container for Windmill is up and running, Nextcloud does not show me any errors. Yet, I can’t see any button to enter the Flow UI. I have deleted and reinstalled the Flow app several times to no avail.

AppApi is configured as follows:

Name: AIO Docker Socket Proxy
Deplyoment method: docker-install
Daemon host: nextcloud-aio-docker-socket-proxy:2375
Nextcloud URL: https://cloud.our-domain.com
Network: nextcloud-aio
no HAProxy PW

“Test connection” shows everything fine, deployment tests run through as well.

Checking the Flow app’s details in the apps menu shows the same data:

Typ: docker-install
Name: docker_aio
Anzeigename: AIO Docker Socket Proxy
GPUs Unterstützung: false
Compute-Gerät: CPU

Do I need to register a separate deploy daemon for setting up Windmill? I have no idea how to debug this, could anyone point me to the correct steps on how to get going?

HaStub · February 20, 2025, 10:13am

I have encountered the exact same issue. Evidently, this problem has been around for quite some time. It might be as trivial as needing to specify a port mapping during the flow (windmill) container startup (for example, using -p 8000:8089), or it could be a more significant matter—but there seems to be very little discussion on the topic. It would be great if a project maintainer could provide some clarity on this issue.