server: Docker expects to be run from the repository root
Maintainers usually reply within 4 days
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker
- Domain
- devops
Research direction
Start by reviewing the Docker build command shown in the issue and the linked pull request #611, then compare how other projects choose Docker build contexts. Done means the server containers can be built from the intended directory without relying on the monorepository root, with the relevant behavior validated.
Written by the indexing model from the issue text.
Description
Currently, the server docker containers all expect to be run from the mono-repository root:
docker build -t basyx-python-server -f Dockerfile ../../..
(where ../../.. is the repository root).
This functional, but arguably somewhat ugly.
Let's discuss the possibility to change this, for example to the ./server directory.
Nevertheless, we should research how other projects do this.
- Dominant language
- Python
- Stars
- 104
- Forks
- 56
- Avg merge
- 12d 13h
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 eclipse-basyx/basyx-python-sdk
-
README CI badge is brokenPossibly taken A pull request linked to this issue is open or already merged. Openbug documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
eclipse-basyx/basyx-python-sdk#656 ·
Maintainers usually reply within 4 days
-
bug server Specification
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
eclipse-basyx/basyx-python-sdk#655 ·
Maintainers usually reply within 4 days
-
bug sdk
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
eclipse-basyx/basyx-python-sdk#634 · 3 comments ·
Maintainers usually reply within 4 days
-
enhancement server
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
eclipse-basyx/basyx-python-sdk#632 ·
Maintainers usually reply within 4 days
-
bug high priority
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
eclipse-basyx/basyx-python-sdk#631 ·
Maintainers usually reply within 4 days
All issues in eclipse-basyx/basyx-python-sdk
Similar issues
-
md/asciidoc/csv: an explicit `encoding="utf-8"` keeps a leading BOM, the auto-detect path drops itOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
docling-project/docling#4846 ·
Maintainers usually reply within 1 day
-
area/sessions comp/dashboard comp/desktop comp/gateway comp/tui duplicate P2 sweeper:risk-session-state type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NousResearch/hermes-agent#138914 · 1 comment ·
Maintainers usually reply within 1 day
-
bot-triaged module: activation checkpointing module: inductor oncall: pt2 triaged
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
[oblt-aw][autodoc] Update PR Actions Detective E2E prerequisites and fix dashboard-format table typoOpendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/oblt-aw#2382 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day