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
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).
The text was updated successfully, but these errors were encountered:
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.
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).
The text was updated successfully, but these errors were encountered: