Documentation for development

[christianlupus]

It might come in handy, if we had a bit more documentation for development:

1. A docker-compose setup with debugging extensions installed
2. Test cases/example data
3. Human-readable form of the steps involved to start debugging (building VUE environment etc), potentially with hits how to avoid caching etc

This issue was an excerpt from recent discussions on other issues and the matrix chat. There are multiple tricks and hints and these should be collected on one place in my opinion.

[christianlupus]

For the first part I created a repository in my personal space: https://github.com/christianlupus/nextcloud-docker-debug. I am unsure if this is a good location in the long-term.

[mrzapp]

@christianlupus do you think perhaps that this could be a wiki page instead of files committed to the repo? At least that way we could keep a well-authored development guide up to date without having to wait for releases.

[christianlupus]

The test cases and manual steps to start the debugging session are well suited for a wiki/github pages. However, the docker files needed to build a docker image with xdebug seems better suited in a repo for me. These files will not change much, only the underlying docker image will evolve over time. But as a dev will rebuild his image, this should be automatically done.

[christianlupus]

I assigned myself here but if anyone wants to participate, just ping me.

[christianlupus]

This has been prepared in #499.