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

Dockerfile for repo #12

Open
kuanb opened this issue Apr 20, 2017 · 1 comment
Open

Dockerfile for repo #12

kuanb opened this issue Apr 20, 2017 · 1 comment

Comments

@kuanb
Copy link
Member

kuanb commented Apr 20, 2017

Why? Dockerfiles are valuable for creating a consistent environment for developers to work in. They also remove any complexities in setting up the appropriate environment within which to run a repo. This is valuable both for persons new to a project when working through examples or documentation, as well as to direct contributors developing new features/fixes.

I've got a Dockerfile that creates a container with the necessary environment dependencies to run UrbanAccess. Given that the dependencies for this are a bit tricky to set up (HDF5 store, etc.), it's valuable (I believe) to have something "set in stone" that can be used by anyone to get something consistent to work in.

I'd be happy to make a PR to include this. I think it would also be helpful for folks who would want to work through example projects without running into setup blockers (also starting example documentation of how to set this up as I infer the workflow from the codebase here - although could make more sense as a Gist or blog post).

@kuanb
Copy link
Member Author

kuanb commented Apr 25, 2017

If Dockerfile wants to be added, and support for Pandana be sustained/made complete, will need to include the additional Dockerfile RUN statements described in Pandana Issue UDST/pandana#70 to ensure Basemap library for matplotlib is available and functional.

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

No branches or pull requests

1 participant