Joda Stößer

You are absolutely right. I fixed the title and edited the issue description.

Glad to hear it. It will improve our ci workflows and keep our repositories clean.

@TkTech @nyuszika7h did Github resolve this in the last years?^^ Or did you do some work on your own code to mitigate it?

This is also discussed in https://github.com/nextcloud/docker/issues/1758

It might be fitting to check if the issue also exists when sharing to circles. If yes, it might be possible to fix them both at the same time.

Currently the OcSMS app doesn't have any integration into the Nextcloud search.

Currently there is no pre-build container available on the Docker Hub from this repository. This repository contains a Dockerfile you need to build yourself. The Readme.md [currently]https://github.com/getgrav/docker-grav/blob/bddde74c5009639b7f14561363e6826ecc8e01b8/README.md doesn't mention this,...

Before this change using/build a Docker image with a new version of Grav didn't actually updated Grav to this version, as the Grav code was persisted in the previous volume....

Most of the time you will only need the `user`, `backup` and `logs` directories outside of your container. I recommend volumes for those three instead of the whole system.

@EgoLeX does the problem persist with the newest, just released version? https://github.com/jhass/nextcloud-keeweb/releases It changes and automates the way the file extension is registered.