PrestaShop / PrestaShop/docker
PS_HANDLE_DYNAMIC_DOMAIN ends up in error for 1.7-7.2-fpm
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 281
- Forks
- 190
- PR merge metrics
- No merged PRs in 30d
Description
When setting PS_HANDLE_DYNAMIC_DOMAIN to true, the docker image ends up failing with the following error:
sed: can't read /conf-available/docker-php.conf: No such file or directory
Tried under prestashop/prestashop:1.7-7.2-fpm, but the error may be in other images as well, as the base files are the same for (most of) the prestashop docker images.
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 by reproducing the failure with prestashop/prestashop:1.7-7.2-fpm and PS_HANDLE_DYNAMIC_DOMAIN=true, then trace where the setting attempts to read /conf-available/docker-php.conf. Check whether the same base files affect other PrestaShop images; done means the setting works without the missing-file error in the affected images.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100