We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
@rsignell-usgs first thank you for all these contributions! 馃帀
Building upon your notebook, I took a stab at creating a panel app for quick interactive rendering of just the plots. See first (green) link here https://github.com/friedrichknuth/covid_dashboard/tree/binder-app
Am wondering if there might be a better way to separate this particular binder environment, so that each commit doesn't trigger a rebuild?
One potential complication I am seeing is that binder app link appears to require a special url path, instead of git-pull
git-pull
https://aws-uswest2-binder.pangeo.io/v2/gh/friedrichknuth/covid_dashboard/binder-app?urlpath=/proxy/5006/dashboard-panel
I can pickup testing tomorrow, but thought to share this for now in case it is a simple fix.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
@rsignell-usgs first thank you for all these contributions! 馃帀
Building upon your notebook, I took a stab at creating a panel app for quick interactive rendering of just the plots. See first (green) link here https://github.com/friedrichknuth/covid_dashboard/tree/binder-app
Am wondering if there might be a better way to separate this particular binder environment, so that each commit doesn't trigger a rebuild?
One potential complication I am seeing is that binder app link appears to require a special url path, instead of
git-pull
https://aws-uswest2-binder.pangeo.io/v2/gh/friedrichknuth/covid_dashboard/binder-app?urlpath=/proxy/5006/dashboard-panel
I can pickup testing tomorrow, but thought to share this for now in case it is a simple fix.
The text was updated successfully, but these errors were encountered: