Blackfire enabled by default?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
Start with the stable31 service invoked by docker compose up stable31 and the existing scripts/php-mod-config entry point. Reproduce the module state with docker compose exec stable31 php -m | grep -i blackfire, then trace how container recreation configures Blackfire. Done means a fresh container follows the documented default and the setting persists across recreation.
Written by the indexing model from the issue text.
Description
Hi, I've noticed a lot of php_network_getaddresses: getaddrinfo for blackfire failed: Name or service not known errors in the nextcloud logs. A quick search surfaced this older issue, which discusses the same: https://github.com/juliusknorr/nextcloud-docker-dev/issues/57
In the end, a changelog entry was referenced, stating that blackfire (and xdebug) should be disabled by default, with scripts to enable / disable them. However, it seems that this is not the case (any more?).
When I start a fresh set of containers (e.g. docker compose up stable31), I see blackfire enabled (docker compose exec stable31 php -m | grep -i blackfire). I can use ./scripts/php-mod-config stable31 blackfire off to disable it, that seems to work. But whenever I recreate the container, it comes back and I have to manually disable again.
- Shouldn't blackfire be disabled by default?
- Is there a simple way to permanently disable blackfire that persists container re-creation?
- Dominant language
- PHP
- Stars
- 190
- Forks
- 103
- Avg merge
- 4h 36m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nextcloud/nextcloud-docker-dev
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
nextcloud/nextcloud-docker-dev#483 · 1 comment · 3 reactions ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
nextcloud/nextcloud-docker-dev#480 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in nextcloud/nextcloud-docker-dev
Similar issues
-
jira-created
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
nunomaduro/phpinsights#745 ·
-
status/awaiting_triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
WordPress/plugin-check#1486 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
az-digital/az_quickstart#6019 ·