Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Previously, I haven't had a nice setup for introspecting
higlass-pythonin a "remote" usage context (beyond ssh-ing onto some remote machine and trying it out). This PR adds a configuration for VSCode Dev Container, which bootstraps a development environment in Docker that can be interacted with on the client. I have been using this to "remotely" host a jupyter notebook within the dev container, and then connect in my browser.As a side note: the
.devcontainerfolder is automatically detected by VS Code, offering new contributors a "one click" environment setup.What was changed in this pull request?
.devcontainer/Fixes #___
Checklist
examples.ipynbnotebookblackon the root directory