Merge pull request #26 from brian-rose/deploy-on-actions

Finish deploy actions business

README.md

@@ -1,6 +1,8 @@
 # The Climate Laboratory
 
 [![DOI](https://zenodo.org/badge/231609808.svg)](https://zenodo.org/badge/latestdoi/231609808)
+![Deploy Book](https://github.com/brian-rose/ClimateLaboratoryBook/actions/workflows/deploy.yaml/badge.svg)
+![Link Checker](https://github.com/brian-rose/ClimateLaboratoryBook/actions/workflows/link-checker.yaml/badge.svg)
 
 ***A hands-on approach to climate physics and climate modeling***
 
@@ -58,9 +60,7 @@ Anyone is welcome to suggest edits or improvements by opening pull requests on t
 
 ## How is the book published
 
-[The book][book] is just the rendered html that results from running `jupyter-book build`. Currently I use the [ghp-import][ghp-import] tool to copy the built html to the `gh-pages` branch on [github][repo].
-
-See the [JupyterBook docs][jbook-publish] for more info on this.
+[The book][book] is just the rendered html that results from running `jupyter-book build`. A new build is triggered on GitHub Actions whenever the sources are updated on the [github repository][repo], and the successful build is deployed to the `gh-pages` branch of the repo.
 
 
 [brian]: http://www.atmos.albany.edu/facstaff/brose/index.html

environment.yml

@@ -16,7 +16,3 @@ dependencies:
   - netcdf4
   - nc-time-axis
   - jupyter-book  # needed to rebuild the book from source
-  - pip
-  - pip:
-    # works for regular pip packages
-    - ghp-import  # used to automatically push the built book to github pages

how-to.md

@@ -1,7 +1,5 @@
 # How to use this book
 
-*under construction*
-
 I wrote this book with a strong emphasis on *reproducibility* of the content.
 For example, most of the figures in the notes are generated interactively,
 often using data pulled from public servers. This means that readers are able
@@ -42,8 +40,6 @@ This should bring you to a login screen. Use your standard UAlbany netid and pas
 
 ## Public users: interact through a cloud-based Binder service
 
-*(currently broken -- working on it)*
-
 This will work well for many of the simple examples,
 but some of the notes require more computational resources.
 Binder is good for tinkering, but there is no easy way to save your work and come back to it.