Manually Register ExApps without the Daemon

ℹ️ Support
1

Hi there,

I added the Nextcloud Assistant today and got it mostly working, except for context_chat. I then noticed my logs were being spammed with errors that it requires the AppAPI and I went down this new rabbit hole.

I have to say I am confused that ExApps MUST use this Deploy Daemon to work based on what I am reading. Surely this cannot be the only way? Docker in Docker or allowing a container access to the Docker socket to create other containers is horrible for security and incompatible with many enterprise security requirements and policies, so surely the team designing this must have added a way to manually connect an ExApp?

I will not enable docker in docker or privileged apps on my Kubernetes cluster, and yet I find myself needing this Daemon because there seems to be no other documented way to deploy the context_chat_backend

I will manually create the Deployment/Pod to run the context_chat_backend and I want to connect it to Nextcloud in my deployment described in my helm chart - Is there a way to register the app without this Deploy Daemon, or put this Deploy Daemon in non-administrative mode so it just acts as a proxy for registration of apps I deploy myself?

2

No responses is not encouraging. If there is no way to make external apps work without giving Nextcloud the ability to create containers, is there at least a way to turn the “context chat” feature of Nextcloud Assistant off so it stops spamming my logs every few minutes complaining that the backend does not exist?

3

I have potentially come across an answer here Run ExApp without Orchestration · nextcloud/app_api · Discussion #416 · GitHub … maybe - It’s not clear if it will do what I need end-to-end - but trying it.