Docker Repository outdated

[tstreibl]

Describe the bug

Hi,

pulling a docker image with 'ghcr.io/cloud-py-api/nextcloud-appapi-dsp:latest' results in Version 1.3.2, although here on github already Version 3.2.0 is available.

The result ist that it's possible to register the App-Api-Deamon in Nextcloud. However when you test the Deamon, the test will fail in the heartbeat step.

Could you please update your docker repository? Sorry that I'm not skilled enough to build the image for myself.

P.S. would be nice when the only Ex App Example in the AppStore ("To Gif Example") would not be restricted to Nextcloud < 29

Steps/Code to Reproduce

see https://help.nextcloud.com/t/appapi-unable-to-update-status/194716/4

Expected Results

docker version should be same as github version

Actual Results

latest docker version ist 1.3.2

Setup configuration

app_api = 1.3.2 nextcloud = latest

[bigcat88]

How on the latest (30?) Nextcloud were you able to run app_api version 1.3.2?
For Nextcloud 30 AppAPI is a bundled app and has a higher version.

[tstreibl]

Sorry for the confusion:

I derived from the cited link, that the problem to fail at the heardbreak check is connected with an outdated app-api version. The user reported, that he got his problem (which seems to be similar to my problem) solved, after updating the app-api. I assumed, that the "app-api Version" is defined by the "nextcloud-appapi-dsp" Version (1.3.2), which I merge by downloading the appropriate docker image. I saw, that at this place already version 3.2.0 is available, which is higher than the docker image I merged.

From your question I assume that the app-api version has nothing to do with the "nextcloud-appapi-dsp" Version, and that the cited docker image is probably up to date? Then you can close this issue. Thanks for looking into it. My nextcloud apps are all up to date.

Background: in the "docker all in one" version the app-api is already integrated in the image. In the docker communite version, this is not the case, so I'm struggeling how to get it running there (changing to the docker all in one version probably would solve my problem, but is not easily done overnight.). In my case I run everything behind traefik, so probaby I failed to properly integrate the service.