Add docker-compose.yml for nextcloud development

[NobodysNightmare]

This is similar to what we already have for Keycloak and GitLab in providing a minimal docker-compose file for integration work.

Ticket

https://community.openproject.org/projects/document-workflows-stream/work_packages/59937/activity

[brunopagno]

I find this briliant. It will change lives 🎉

Only thing I believe we should change is the filename from docker-compose.yml to docker-compose.override.yml.

The rest are a few observations based on my own setup, but it's okay if they are not included.

[brunopagno]

I needed to include the cron override on mine as well

  cron:
    volumes:
      - ${APP_DIR:-./../../custom_apps}:/var/www/html/custom_apps
    networks:
      - external

[NobodysNightmare]

Can you post your full cron service definition? I only have the nextcloud service running locally for me.

[brunopagno]

I was referring to the cron definition in the integration project.

[NobodysNightmare]

I see. Makes sense, if we need cron, we should add it to this compose file. Do you know if cron is needed for our integration purposes?

[brunopagno]

I do not know. Briefly reading does not sound mandatory. But probably useful to have.

[NobodysNightmare]

I added a cron service as well now. Looking at my local installation, it seems to be working.

[NobodysNightmare]

I find this briliant. It will change lives 🎉

Only thing I believe we should change is the filename from docker-compose.yml to docker-compose.override.yml.

The rest are a few observations based on my own setup, but it's okay if they are not included.

I am calling this docker-compose.yml because it's not an override file, but a base file. Otherwise: What's the base file we'd be overriding? I would want to avoid providing an override for a file that's not part of this repository, because then the original file could change without us noticing and thus the override would override wrongly.

[brunopagno]

What's the base file we'd be overriding? I would want to avoid providing an override for a file that's not part of this repository, because then the original file could change without us noticing and thus the override would override wrongly.

I guess that makes sense. It's not necessarily related to the openproject-nextcloud-integration, is it? I wonder if it would become more confusing in the future. But I see the last steps of the readme are already installing the whole thing.