OpenConext / OpenConext/OpenConext-BaseContainers
Xdebug is not enabled
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
Hi!
I could not help myself, and had to give the DevConf based Stepup dev-env a spin! My use case was to debug an issue we encountered in Stepup-Gateway. But that's not important now.
After a quite streamlined setup, only hindered by a missing Yubico config file and a local occupant on port 80, I had a running Stepup dev env with Gateway serving my local code 🦾
I did however noticed that Xdebug was not enabled on the gateway-dev image. After investigating, I noticed that Xdebug was installed, but not enabled.
The && docker-php-ext-enable xdebug portion of the code pasted below is not executed. Suggesting the pecl install command returned a non-zero response. Should be an easy fix by making it into a twoliner, or by using the ; separator?
RUN pecl install xdebug-2.9.0 && docker-php-ext-enable xdebug
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start with php72-apache2-node16-composer2/Dockerfile at the linked line and inspect how the Xdebug installation command behaves during the gateway-dev image build. Rebuild the image and verify that Xdebug is enabled in the resulting PHP environment; done means the gateway-dev image exposes Xdebug for debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php
- Domain
- build-system, devops
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100