Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dev environment guide #11

Open
avirshup opened this issue Jul 17, 2016 · 1 comment
Open

Dev environment guide #11

avirshup opened this issue Jul 17, 2016 · 1 comment
Assignees
Milestone

Comments

@avirshup
Copy link
Contributor

avirshup commented Jul 17, 2016

Need easy-to-follow instructions for preparing a dev environment.

This would probably include:

  • pull MDT (and possibly nbmolviz and pyccc as well)
  • pip install -e any relevant packages
  • install docker, pull the images.
  • install python dependencies locally?
  • know how to build new docker images

Still a big problem that docker images with MDT code in them will lag behind your dev version. Some sort of solution that lets us mount the code into the containers would be ideal. Possibly need to have a custom "dev" mode in CCC that would let you do this.

We need a better way to do interface development - a JSON interface + sending the code functions every time would probably fix this.

@avirshup avirshup added this to the 0.8 milestone Jul 17, 2016
@avirshup avirshup self-assigned this Aug 2, 2016
@avirshup
Copy link
Contributor Author

avirshup commented Jun 9, 2017

In progress at /DEVELOPMENT.md

TODO:

  • more Conda, less PyEnv
  • dev version synchronization with nbmolviz
  • Encourage py3 as the target, then backport as necessary to py2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant