escoand
escoand
Did not test, but this should fix it https://github.com/nextcloud/server/pull/43392
As a workaround I use this in a docker-compose file: ```yaml nextcloud: image: library/nextcloud:26.0.1-fpm-alpine ... command: >- sh -c ' { echo pm=dynamic; echo pm.max_children=120; echo pm.start_servers=12; echo pm.min_spare_servers=6; echo...
@rugk I try to avoid additional files and just have it in the docker-compose. To circumvent this problem you could use: ```yaml nextcloud: image: library/nextcloud:26.0.1-fpm-alpine ... command: >- sh -c...
> Please note that I have still have concerns around dynamic definitions in this case. The usual behavior is to have explicit sensor definitions. Only "hubs" such as deconz tend...
What does "I am still not satisfied" mean? No merge with this approach?
I've reverted the update entity. @mib1185 are you interested in review?
I changed the implementation to static sensors. I hope this is as requested.
When will this be released as a new docker image?
I'm using caddy as reverse_proxy and `nextcloud:fpm-alpine`, so I could not connect to the nextcloud container directly, as this is not speaking HTTP. First I had the problem with not...
@raimund-schluessler exactly, I'd the same problem but mapping the ip solved it.