Skip to content

server: Add image:-based compose files alongside compose.dev.yml - #659

Open
paul-gerber-svg wants to merge 2 commits into
eclipse-basyx:developfrom
rwth-iat:improve/example-configs-use-published-images
Open

paul-gerber-svg wants to merge 2 commits into
eclipse-basyx:developfrom
rwth-iat:improve/example-configs-use-published-images

Conversation

@paul-gerber-svg

Copy link
Copy Markdown
Contributor

The example configurations under example_configurations/ only had compose.dev.yml, which builds the image locally. The READMEs already mentioned the pre-built DockerHub images, but no compose file actually used them.

This change adds a compose.yml per profile (repository, registry, discovery) that pulls eclipsebasyx/basyx-python-*:latest instead of building. docker compose up now uses the published image by default; compose.dev.yml remains for building from source.

While testing this against the real images, the repository and registry READMEs turned out to reference outdated API base paths (/api/v3.0/ and /api/v3.1.1/) from before all profiles were unified to /api/v3.1. This is also fixed.

Fixes #640

Previously, the example configurations in `example_configurations/`
only had `compose.dev.yml`, which builds the image locally from
source. The READMEs already referenced the pre-built DockerHub images
by name, but there was no compose file that actually used them.

This adds a `compose.yml` per profile (repository, registry,
discovery) that pulls the matching `eclipsebasyx/basyx-python-*:latest`
image instead of building. `docker compose up` now uses the published
image by default; `docker compose -f compose.dev.yml up` remains the
explicit way to build from source for development.

Fixes eclipse-basyx#640
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant