Skip to content

Conversation

@stackcoder
Copy link

Development containers / devpod offer a standardized, reproducible way to define development environments.

While attempting to build the project locally, I ran into a few issues that made setup challenging:

  • Poetry and requirements.pip appear out of sync, so there’s no single source of truth for Python dependencies
  • The published container image (rfquack/rfquack ) is several years old
  • The Dockerfile installs dependencies by copying the full repo, then the Makefile mounts the repo again as a volume
  • The base image python:3.10-slim is Debian Trixie, though some scripts call it Ubuntu

To proceed, I made some adjustments and proposed a devcontainer-based setup. Please let me know if this proposal is acceptable and if I should complete the work?

Add a VS Code DevContainer for a standardized development
environment. Consolidate dependency management under Poetry,
remove redundant requirements and duplicate package installs.
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