Skip to content

Conversation

@edmundmiller
Copy link

  • Add development container configuration for MegaQC
  • build: Migrate to uv
  • build: Update pyyaml to 6.0
  • build: Add NODE_OPTIONS for legacy OpenSSL support in webpack scripts
  • build: Lock down versions for megaqc initdb

- Introduced devcontainer.json for VS Code setup with Node.js, PostgreSQL, and essential features.
- Created docker-compose.yml to define app and PostgreSQL services.
- Added Dockerfile to set up the development environment with Python, Node.js, and necessary dependencies.
- Included README.md for guidance on using the development container and setup instructions.
- Implemented setup.sh script for environment initialization and dependency installation using uv.
- Added `importlib_metadata` as a dependency for Python versions < 3.8.
- Downgraded `flask-marshmallow` version to 0.14.0 in `uv.lock`.
- Updated version retrieval in `megaqc` package to use `importlib.metadata` with a fallback for older Python versions.
@multimeric
Copy link
Collaborator

Not opposed to any of these changes, but the build will probably be tricky to get working, and I don't have much time to look at it.

With the dev container it would be great if you could find a way to re-use some of the dependency logic from the production container. Is an install script a good idea? Or just image inheritance? You also seem to install poetry in the container which shouldn't be used any longer.

build: Lock down versions for megaqc initdb

Not sure what you mean here. The dev dependency versions?

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.

2 participants