Advice about docker socket configuration

[DaphneMuller]

An integration partner reached out to me.

They are trying to set up the AppAPI in Nextcloud using Docker, but are encountering issues with the Docker socket configuration. They previously attempted to create a volume for the Docker socket within the Nextcloud AIO container, but it wasn't successful.

Could you advise on the recommended approach for configuring Docker access for the AppAPI in a Nextcloud AIO environment or a link to the relevant documentation?

Are there any specific considerations we should be aware of when using volumes for the Docker socket?

[DaphneMuller]

@bigcat88

[bigcat88]

In AIO everything should work out of the box, where the DeployDemon is created automatically.

If they have some non-standard scheme, they can look at what parameters the default daemon is created with:

https://cloud-py-api.github.io/app_api/DeployConfigurations.html#nextcloud-in-docker-aio-all-in-one

After creating the Daemon, the easiest way to check it is with the "TestDeploy" button

To say something more specific, we need to know at what step of TestDeploy - they have an error

[andrey18106]

@kevmax1 Hi! Sorry for taking this too long.
Thank you for logs. We were able to reproduce it locally and confirm the problem, looks like a bug. We'll update you on that tomorrow.

[andrey18106]

@kevmax1 It was a bug with cache (in your setup APCu is used), will be fixed in AppAPI 3.0.0, which is going to be released next week.

[kevmax1]

Hi @andrey18106 ,

Thank you for the update and for identifying the issue with the cache. We're looking forward to the release of AppAPI 3.0.0 this week.

Thanks again for your help!

[andrey18106]

@kevmax1 Hi!

Thank you for your patience.
AppAPI 3.0.0 is released, please verify if it works for you now.

Note: According to your docker-compose file - don't forget to configure Deploy daemon to use Nextcloud Url = http://nextcloud29 (name of the nextcloud container) and add this domain to trusted_domains (occ config:system:set trusted_domains 0 --value nextcloud29 --type string, and Network should be set to your docker-compose project's network usually created with the name of the folder and _default prefix with Bridge driver.

[kevmax1]

Good evening @andrey18106,

I hope this message finds you well.

Thanks to your invaluable support, we have successfully resolved the previous issues and have now begun working on our external application, CADViewer. At this stage, we have encountered a few questions where we would greatly appreciate your expertise:

1.⁠ ⁠What is the recommended approach for testing our locally developed external app within Nextcloud?
2.⁠ ⁠We are unable to locate any documentation regarding the implementation of an interface that allows users to interact with our external app after selecting it from a file's context menu. Our goal is to enable users to view files of a specific type and provide a set of related functionalities.

Your guidance on these points would be greatly appreciated.

Thank you once again for your assistance.

[DaphneMuller]

I received an additional email from the same people related to this discussion:
1: All the samples are based on a container pull from ghcr.io, but what is the recommended approach for testing our locally developed external app with nextcloud (no guidance written up)?

2: The Nextcloud external app samples shows how to exchange files. etc., but there is no examples nor is there any documentation on how to deploy an interface?