pangeo-data/cookiecutter-pangeo-binder

Pangeo-Binder Cookiecutter Template

cookiecutter-pangeo-binder's Issues

update cookie cutter?

A lot of developments have happened with dask server extension recently. Do we want to update this cookie cutter?

This repository lacks a setup.py

@jhamman is it possible that you have this on your local machine and that it wasn't checked into git?

tests to confirm pangeo binder configuration successful

I'm working on getting a lidar point cloud processing pipeline running on Pangeo. Because of the lidar software requirements necessitating root priveleges to set up, I had to resort to using a Dockerfile to handle the installation and configuration. I've integrated all the requirements in the cookie cutter environment.yml into my own package's environment.yml and consolidated all the commands from the cookie cutter start, postBuild, and apt.txt files into my Dockerfile.

I am wondering if there's a way for me to confirm whether the pangeo configuration is actually fully working as expected once the build completes. Are there any test scripts that could be run for this?

Cookiecutter Binder unable to initialize session

When I create a my own Binder using this Cookiecutter, I get the following error log which ends the session initialization:

Has the installation method for intake-xarray changed since the Cookiecutter has been updated?

setting environment variables

I hope this is an OK place to ask this question...I have made a simple pangeo binder. I copy in some binaries using curl in my postBuild script. But...I can't figure out how to add their location to the system path using an environment variable. Is that even possible?

Many thanks!

Deprecate and close this repo?

AFAICT, this repo no longer works and is superceded by pangeo gallery.

We should archive it.

Any objections?

play-by-play cookie cutter test

I successfully used cookiecutter-pangeo-binder to create a repo called "hurricane_trimesh":
https://github.com/rsignell-usgs/hurricane_trimesh

Here's the play-by-play:

1. On Github GUI, created a new repo called "hurricane_trimesh".

2. Answered the questions, using "hurricane_trimesh" as project name:
   

3. Verified that hurricane_trimesh folder got created locally:
   

4. Pushed to github following the github instructions for creating a new repository from the command line:
   

5. Added my notebooks, changed the environment.yml to suit my environment needs, and modified postBuild to specify a specific version of the jupyterlab-manager extension that is compatible with the specific version of the jupyterlab python package.

6. Clicked the "launch binder" button and waited (about 20 min) for binder.pangeo.io to build and launch.

7. Started up trimesh notebook: the kube cluster spun up in only a few minutes.

8. Calculated the max water level and interactively browsed the output with pyviz:
   

Thanks @jhamman for an awesome tool!

Add Binder badge link to README.rst