Skip to content

Update docker compose#88

Open
Yannicked wants to merge 10 commits into
iterorganization:developfrom
Yannicked:feature/docker-compose
Open

Update docker compose#88
Yannicked wants to merge 10 commits into
iterorganization:developfrom
Yannicked:feature/docker-compose

Conversation

@Yannicked

Copy link
Copy Markdown
Collaborator

Updates the docker build files

@Louwrensth Louwrensth left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work.
I was looking to update it too.

Please have a look at my comments

Comment thread docker-compose.yml
Comment thread docker-compose.yml
Comment thread docker-compose.yml
Comment thread Dockerfile
@Louwrensth

Louwrensth commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

After our meeting with @olivhoenen I understood I could add small work to your fork/branch directly

I've added some commits I had laying around... the last one is probably not what you want -- but how can we run alternative python versions with a single uv.lock file?

@Yannicked

Copy link
Copy Markdown
Collaborator Author

After our meeting with @olivhoenen I understood I could add small work to your fork/branch directly

I've added some commits I had laying around... the last one is probably not what you want -- but how can we run alternative python versions with a single uv.lock file?

uv is designed to support multiple Python environments in a single lock file by default, so we shouldn't run into any issues running alternative versions.

Comment thread docker-compose-pyver.yml

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the motivation for running all three Python versions simultaneously?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was a request to have them running for development/debugging purpose only. IIRC, @prasad-sawantdesai was working on a feature (with the simdb dashboard) that had a bug for one of the Python versions.

@prasad-sawantdesai prasad-sawantdesai Jun 16, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This feature we could use in GitHub actions to test SimDB server with different Python versions. Main purpose is that one should be able to switch to different branches/PRs to verify behavior quickly..

main --> Currently installed production version (Always available)
develop --> development version (Always available with updated develop version, restarts with new changes)
Pull requests --> to test pull requests (On demand)

symlink validation-schema.yaml
simdb.cli.remote_api.RemoteError: Cannot process IMAS data as server.imas_remote_host configuration option not set
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.

Docker recipes to ease distribution and deployment of the server

3 participants