could not use another port for testing in local (only port 80 that works in port forwarding)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, docker-compose, wordpress
- Domain
- devops
Research direction
Start by reproducing the port-forwarding behavior from compose.yaml, comparing the working 80:8080 mapping with another host port. Read the referenced Dockerfile and verify which port the container exposes or listens on. Done means the project works locally through a non-80 host port, with the working mapping documented or tested.
Written by the indexing model from the issue text.
Description
using port 80, the project work just fine, but when i try to tweek it a little bit to use other port, it could not works.
here's my compose.yaml
services:
wp:
build:
context: .
dockerfile: Dockerfile
ports:
- 80:8080
- Dominant language
- PHP
- Stars
- 21
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
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.
More from fly-apps/wordpress-sqlite
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
fly-apps/wordpress-sqlite#4 · 3 comments ·
All issues in fly-apps/wordpress-sqlite
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
pluginsGLPI/datainjection#673 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
octobercms/october#6130 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
getgrav/grav-plugin-form#656 ·
-
customer-support needs-triage Platform(Default)
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 88/100