Docker-based development #9
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Move update-pipenv-lock to a dev/ directory, to start a trend of keeping scripts there. Modify the Dockerfile such that it can have a dev instance and a production instance. Remove cargo and rust, as ruff no longer needs them (This saves about 600 MB off of the size of the container)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A first pass of some containerized tools I did a while back that might benefit someone else.
Restructured the Dockerfile to allow for linters and the like to run in a sub-container and wrote a little script so that someone can easily run ruff on their code from a dockerized version of Python.
If I have some time, I might extend this to a dev container implementation for folks that use VSCode, but we'll see.