You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VS Code has a great feature where you can work on a repo fully within a Docker container, either on your computer (called Remote - Containers) or remotely on Azure hosted by them (called VS Code Online). This could be particularly useful for setting up a quick dev environment to work on the pandas codebase, and not have to manually go through the setup steps in the docs.
I will try to put something together for this, figured I'd first start an issue here so that if anyone else is working on this we can collaborate and not duplicate our work.
The text was updated successfully, but these errors were encountered:
yehoshuadimarsky
changed the title
ENH: Create a .devcontainer.json file for VS Code Online work
ENH: Create a devcontainer.json env to work with VS Code in Containers
Jan 2, 2020
VS Code has a great feature where you can work on a repo fully within a Docker container, either on your computer (called Remote - Containers) or remotely on Azure hosted by them (called VS Code Online). This could be particularly useful for setting up a quick dev environment to work on the pandas codebase, and not have to manually go through the setup steps in the docs.
Per the VS Code docs (https://code.visualstudio.com/docs/remote/containers and https://docs.microsoft.com/en-us/visualstudio/online/reference/configuring) you can create a
.devcontainer.json
file in the root of the repo that will contain everything needed to setup the environment, similar to the condaenvironment.yml
file. You can also create a DockerFile inside adevcontainer
folder to use with thedevcontainer.json
file.I will try to put something together for this, figured I'd first start an issue here so that if anyone else is working on this we can collaborate and not duplicate our work.
The text was updated successfully, but these errors were encountered: